Cello VS pycparser

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.

In python, we have pycparser https://github.com/eliben/pycparser to parse C files into a tree.

I found pycparser which can probably do what you need, but it might not be very easy to use.

You can also use pycparser[0]. It is fully compatible C99, but be careful it doesn't support gnu extensions (like attributes, #indent, asm() ...). You can however work around most of them by -D defining them to empty macro in the argument.

[0] https://github.com/eliben/pycparser

I wrote that tiny C compiler in Python and chose pycparser as the starting point. If you run C source code through pycparser it yields an Abstract syntax tree (AST) which is an in-memory, fine-grained tree representation of the C source code (for example, compound expressions are represented as binary trees that obey operator precedence rules which is extremely helpful).

The difficulty is that in c you can do all kinds of weird and wonderful things... Doing it just by a text analysis of three code is going to be difficult to say the least. You could look at something like this parser though I suspect you might get better results using some of the existing utilities out there

Just find a C parser/lexer/whatever that'll handle the parsing for you. You can probably use it to determine where each function starts, where it ends, what it's called, etc.

In terms of functionality the PipelineC project is pretty mature. But the back end implementation is hacky involves far to much reliance on a pycparser setup I dont understand (other than basic AST traversal was all needed). And as I slowly look to add not-strictly-C language concepts I would love to be working with someone who knows whats going on with compilers, syntaxes, intermediates. Some kind of Rust or C++ front end would be cool - template types and constexpr like things are something I am really missing being limited to C at the moment. I'll teach you FPGA things in return :-p