Workshop Tools

A compiler will translate your source into executable code. Yet many more tools are needed to work effectively with the ‘Best-Language, Ever’ – and we are not talking about debuggers! The Castle workbench can do so much more to make your code outstanding.

Probably you have many questions about the software. About its metrics: like the Fan-Out of a given class or its Cyclomatic-Complexity. Or merely like to k Often this isn’t too complicated. But the amount of error-prone work is dramatic. Castle comes with tools that provide the answer.

Read more ...

The Sieve demo (start/DRAFT)

To show some features of CCastle, I use ‘the sieve’, short for the Sieve of Eratosthenes. An old, well known, algorithm to find prime numbers; with impliciet concurrency.

With an almost trivial implementation, many “CC concepts” can be shown. In only a handful of lines….

Read more ...

Structure the md-content

Within the concept as described in Revealjs + Markdown, and with The html-template composed as given, we can start autoring webslides in md. Aside of standard-md, some extra “structure” is are available, to split the md-file into (sub)slides, and animate its components.

Read more ...

Pre/In/PostFixes in generated CC2Py code

The CC2Cpy compiler generated C-code, using a lot of pre-, in- and postfixed.

They are documented later ..

Read more ...

Modeling & Rendering Components & Friends

Any compiler will read & parse the source, convert it into an abstract natation (like the AST) and write the result back in a lower-language, or “binary format”. We have spend several posts on the parsing phase. This one focus on the last part: rendering the model into “generated C code”.

The goal is not to design “all & everything”. We pick some details, do some experiment (typically in Jupyter/IPython Notebook), and the lessons-learned are documented here.

Read more ...