SAsargstuff·Jul 1, 2024
modern visual punch card take on [0]?
Run / jump through hoops with any C code without concerns of syntax/error issues.
[0] : c99.sh : https://github.com/RhysU/c99sh
In Paper Compiler [video]RhysU
c99sh
Shell2014–2024
RhysU / c99sh
c99sh
A shebang-friendly script for "interpreting" single C99, C11, and C++ files, including rcfile support.
4Distinct people
12Mentions
0Explicit recommenders
114GitHub stars
What to know before exploring
What it is
A shebang-friendly script for "interpreting" single C99, C11, and C++ files, including rcfile support.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year12 dated mentions
Observed mentions: 2014-01-02 02:29:55 UTC to 2024-07-01 12:58:38 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
12 sourcesA shebang-friendly script for "interpreting" single C99, C11, and C++ files, including rcfile support: https://github.com/RhysU/c99sh/blob/master/c99sh
Use gnuplot to plot one or more files directly from the command line: https://github.com/RhysU/gplot/blob/master/gplot
In Ask HN: Can I see your scripts?Plot one or more files from the command line: https://github.com/RhysU/gplot
"Interpret" C and C++ files: https://github.com/RhysU/c99sh
In Ask HN: What are some tools / libraries you built yourself?> I feel like the fine grained low level control is exactly the reason they chose C in the first place
That's not the only reason, there is also simplicity, static typing and performance. If you favor the later two for whatever reason it can be used in places where you'd normal write a python/shell script or small program without too much extra effort (see https://github.com/RhysU/c99sh or suckless tools). Complexity is where Cello seems to fall down though, it seems like it introduces much more complexity than just using plain C with a decent "standard" library like glib.
In Cello – High Level CThirded, especially on the pragmatism, this by far the most pragmatic programming book I've ever read. I fell in love with the C as a scripting language parts (https://github.com/RhysU/c99sh), now I don't have much of a use for a scripting language to sit between bash and "proper language" (apart from some occasional awk).
In Modern C, Second Edition> Well, with compiled languages and multiple servers it does get a bit more complex.
Compiling (and basically anything) can be done as a cgi script (https://github.com/RhysU/c99sh), I bet you could go a long way with that on a network drive or with an rsync daemon.
In Dark emerges with ‘deployless’ software modelI find GCC compile times to be unnoticeable and perfectly usable as a scripting language, certainly competitive with the startup time of many scripting languages. By the time you're getting to noticable compile times your well into "this should be a proper project" territory, but everything from small scripts to simple GUI programs compile quickly. I wrote my own shebang scripts but there's a more full featured implementation here: https://github.com/RhysU/c99sh
In Fast Compilers for Fast ProgramsI bought this on your recommendation and have to say how great it is so far, readable, just opinionated enough, reasonably concise and very pragmatic, the exact opposite of every other C book out there. It's not great for completely new programmers but it's fantastic for everyone else.
That first chapter alone and the C shebang (https://github.com/RhysU/c99sh) walkthrough put together so many ideas I've never thought or heeard of. It makes C usable in ways that you'd typical use something like python for.
In Best way to learn C in 2019?Self-plug: https://github.com/RhysU/c99sh
A shebang-friendly script for "interpreting" single C99, C11, and C++ files, including rcfile support.
No interpreted mode.
In Show HN: Cpi – Immediately compile and execute c++ program like a scripting langShameless self plug on alternative:
https://github.com/RhysU/c99sh
Ditto: Shebang, stdin
Extras: Automatic includes, nice error reporting, RC files, pkg-config, and C++ too.
Lacks: Multiple file
In C – Compile and execute C “scripts” in one goRelated: https://github.com/RhysU/c99sh
In C – Compile and execute C “scripts” in one goRhysU/c99sh: cppsh for C99 with rcfile support
2 points · Open discussion