cedro VS Cello

I’ve built it for now in a separate branch called “self”:

    git clone -b self https://github.com/Sentido-Labs/cedro.git

Currently, it does not make any difference whether this is one token or more because it is sent to the compiler exactly the same as it came in, but you could write a macro/plugin (src/macros/] that recognized this pattern and inserted a space right before the minus “-” sign.

Hi, when I presented the first release here 8 months ago (https://news.ycombinator.com/item?id=28166125) it got interesting comments and today I’ve made a new release with additional features:

- Break out of nested loops: break label; (https://sentido-labs.com/en/library/cedro/202106171400/#labe...)

- Notation for array slices: array[start..end] (https://sentido-labs.com/en/library/cedro/202106171400/#slic...)

- Loop macros: #foreach { ... #foreach } (https://sentido-labs.com/en/library/cedro/202106171400/#loop...)

The possibility of loop macros was discussed in this thread: https://news.ycombinator.com/item?id=28166698

At the time I hadn’t figured out how to make it useful without type information, but now it works. The same for the array slice notation: it took me a while to figure out how to make it do something useful without reflection, with a purely syntantical transformation.

Loop macros are useful for the kind of things for which you would use x-macros (https://en.wikipedia.org/wiki/X_Macro), with the advantage that it does not pollute the global namespace with macro names and the body of the macro stays more similar to the final result, which makes big macros easier to read.

Since it runs before the standard C preprocessor it can do things like building up `_Generic` macros as shown in the loop macro vec example: https://sentido-labs.com/en/library/cedro/202106171400/#loop...

Source code (Apache 2.0 license): https://sentido-labs.com/en/library/ or https://github.com/Sentido-Labs/cedro

If pre-processing your code is an acceptable compromise, my Cedro pre-processor has that feature: passing a file through it produces standard C code for your compiler, and it includes a wrapper cedrocc that can be used in Unix/POSIX-style systems like Linux as a drop-in replacement for GCC: https://github.com/Sentido-Labs/cedro/

What I’d like to do is a quick proof-of-concept to see whether whatever instructions are available in my CPU can be leveraged for UTF-8 en-/decoding.

For instance, does it work any better than my C implementation? https://github.com/Sentido-Labs/cedro/blob/master/src/cedro....

Maybe the compiler already compiles that to an optimal SIMD version, I don’t know.

Yes, that's C. C macros can take you quite far. Unfortunately because it's just a bunch of macros, it's quite brittle. Like high level abstractions created with macros in assembly language. You have to do all the checking and reasoning about it since the compiler cannot.

[1] https://libcello.org/

It took me a long time to understand, coming from higher level programming, that a lot of exactly that "higher level" is just systematic fat pointer conventions. And because pointers-with-metadata is not a first-class language construct, we invent all these languages that codify a particular fat pointer convention. Cello is an example of what kinds of abstractions can be built on top of a tiny little bit of (non-native) fat pointer convention.

There is a lightweight object oriented extension to C called Objective-C [1] that unfortunately never gained much traction outside the NeXT/Apple ecosystem. There is also Cello [2].

[1] https://en.wikipedia.org/wiki/Objective-C

[2] https://github.com/orangeduck/Cello

Regular expressions library to validate information before dumping to rocksdb.

https://www.gnu.org/software/libc/manual/html_node/Regular-E...

Non-critical implimentation fun, use cello [1] for 'gawk' functionality in C with C++ objects/classes.

[1] https://libcello.org/

You can achieve a fairly decent runtime safety for some types of project. Check out libcello and my own monster (libstent, lame presentation).

towards lisp related data structures / algorithms (aka recursive tree data structures & algorithms).

So, no distinction between metadata vs. structual storage unless noted.

Anything beyond that tends towards masters & upper level undergraduate level material. aka review the implimentation of a programming language for algorithm & data structure usage per language features.

aka Autonoma / regular expressions backround: Lisp in Small Pieces by Christian Queinnec; ; https://github.com/aalhour/awesome-compilers; On Lisp by Paul Graham; Let over Lambda by Doug Hoyte; C 'macro's pushed to maximum effect : https://libcello.org/

    Left out Comparison of languages; Transform from lang a to lang b; and language implimentation as discussions tend to assume masters / upper level undergraduate knowledge

with skills like this, mind to push cello forward? https://github.com/orangeduck/Cello really like it but not skillful enough to do it myself.