cedro
ciao
cedro | ciao | |
---|---|---|
6 | 3 | |
44 | 243 | |
- | 2.1% | |
3.4 | 8.8 | |
about 1 year ago | about 2 months ago | |
C | Prolog | |
Apache License 2.0 | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cedro
-
OOP in C
I’ve built it for now in a separate branch called “self”:
git clone -b self https://github.com/Sentido-Labs/cedro.git
-
What do you think about a C transpiler?
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.
-
Show HN: Loop macros, label break, slices in C with the Cedro preprocessor
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
-
is there a c function exit hook?
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/
-
Keeping POWER relevant in the open source world
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.
ciao
- PHP: Prolog Home Page
-
An embeddable Prolog scripting language for Go
Some Prolog systems (like Ciao Prolog https://github.com/ciao-lang/ciao/blob/master/core/lib/forei...) implement bidirectional foreign interfaces. Once you have C bindings it is easy to write bindings from Rust, C++, or any other language (that can interoperate with C). I give here some details about Ciao because this is the system I know better but it should be similar for other popular Prolog implementations.
The tradeoffs depend on the complexity of the Prolog code and your needs for performance and features: pure LP, Prolog (search+unification+cut), garbage collection, dynamic database updates, constraint domains, etc. The Ciao Prolog engine is around 300-400KB. Adding a few libraries, compiler, etc. it goes to 2MB. Naive Prolog systems can be one order of magnitude smaller at the cost of sacrificing ISO compatibility, performance, etc. Note that "performance" can be very misleading. Some Prolog programs may run particularly fast in some Prolog system and very badly in others.
- Keeping POWER relevant in the open source world
What are some alternatives?
cyclone - Cyclone is a type- and memory-safe dialect of C
prolog - The only reasonable scripting engine for Go.
cake - Cake a C23 front end and transpiler written in C
Prolog-to-List-Prolog - Converts Prolog algorithms to List Prolog algorithms
a2i
trealla-js - Trealla Prolog for the web
ooduck - Duck-Typing C library based on ooc.pdf
go - Trealla Prolog embedded in Go using WASM
a2o
librealsense - Intel® RealSense™ SDK
php - Prolog Home Page