cedro
carbon-lang
cedro | carbon-lang | |
---|---|---|
6 | 174 | |
44 | 32,216 | |
- | 0.3% | |
3.4 | 9.8 | |
about 1 year ago | 1 day ago | |
C | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
carbon-lang
- Carbon Copy Newsletter No.2
-
Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
The roadmap for Carbon [0] mentions wanting to have basic, non-trivial programs written in Carbon by the end of 2024. They're aiming for a v0.1 release in 2025. If it gains traction, they're aiming for a v1.0 beyond 2027.
I don't think anyone outside Google will seriously adopt this before it reaches v1.0. Even within Google, they may choose other options.
[0] - https://github.com/carbon-language/carbon-lang/blob/trunk/do...
- Carbon Language Newsletter, the Carbon Copy, February 2024
-
Odin Programming Language
Carbon was started by Chandler Carruth, at Google, but they wanted to move it to broader governance quickly. It's not under the Google GitHub today, but its own org.
https://github.com/carbon-language/carbon-lang/blob/trunk/do...
-
C++ Should Be C++
What do you think about Carbon[1]? I am hopeful.
[1] https://github.com/carbon-language/carbon-lang
- The NSA advises move to memory-safe languages
- Carbon Language: An experimental successor to C++
-
Toward a TypeScript for C++"
https://github.com/carbon-language/carbon-lang/blob/trunk/do...
next year 0.1 will be usable, 1.0 is about 3 years away, sigh, back to my rust fight
-
Programming Languages Every Developer Should Watch Out For
1. Carbon
What are some alternatives?
cyclone - Cyclone is a type- and memory-safe dialect of C
rust - Empowering everyone to build reliable and efficient software.
cake - Cake a C23 front end and transpiler written in C
crubit
a2i
cppfront - A personal experimental C++ Syntax 2 -> Syntax 1 compiler
ooduck - Duck-Typing C library based on ooc.pdf
Odin - Odin Programming Language
a2o
go - The Go programming language
librealsense - Intel® RealSense™ SDK
hylo - The Hylo programming language