| jpl-mode | jsource | |
|---|---|---|
| 1 | 18 | |
| 7 | 640 | |
| - | 1.4% | |
| 2.8 | 9.6 | |
| 4 months ago | 10 days ago | |
| Emacs Lisp | C | |
| GNU General Public License v3.0 only | 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.
jpl-mode
-
Embedding J
Another module that does the same thing, that I referred to: https://github.com/jitwit/jpl-mode/blob/a/jpl-module.c
jsource
-
Crafting Self-Evident Code with D
The one other example I know that morphs the language to that extent and to the detriment of readability by C programmers is the J interpreter[1,2]. But, once again, nobody (that I’ve read) claims it’s good or clear C. (Good C for those who speak J, maybe; I wouldn’t know.)
For a way to morph C syntax that does make things better, see libmill[3].
[1] https://code.jsoftware.com/wiki/Essays/Incunabulum
[2] https://github.com/jsoftware/jsource/tree/master/jsrc
[3] https://250bpm.com/blog:56/
- Show HN: Gemini client in 100 lines of C
-
Can anyone identify what this code does ?
Oh damn Whitney C representation.
-
C is the most dysfunctional non-esolang on the planet, precisely because everyone insisted on it being "just simple pointers"
I develop J btw
-
Want cleaner code? Use the rule of six
No, it was rhetorical, because it's obviously (to an APL-family programmer), not bad!
Your cultural prejudice is showing. There are good reasons APL is written the way it is, and this example is simply bringing those benefits to C by writing it in the dense APL style. There are other APL derivatives, like J[1] that are written the same way. These projects are well-maintained. They aren't collapsing under a load of technical debt. The style works. To them, it's clean code.
[1]: https://github.com/jsoftware/jsource
-
Ask HN: Is this how anyone programs?
Recently, I wanted to write a simple piece of code in J, but immediately found a bug. I went ahead to fetch the source to see if I can fix it. But, hell no. I couldn't believe my eyes. Is this how someone programs, really? I just can't believe it didn't go through some kind of obfuscator.
Here are some samples, but almost anything in the repository is beyond me:
https://github.com/jsoftware/jsource/blob/master/jsrc/xo.c
-
Jd
You can view the code, but is not open source: https://github.com/jsoftware/jsource/blob/master/license.txt
-
Someone earlier linked to Arthur Whitney's style of coding in the comments. Can we discuss this further? I am disturbed by what I saw.
This is the same dense style used in J.
-
Why does old C code often declare functions or global variables in the scope it's used, rather than at the top of a source file or a header file?
All-in-all this example doesn't seem too bad. It's clear what happens and is easy to follow. If you wan't to see something remarkably terribly, check out Whitney style. It's used in APL/J/K family interpreters. Keep in mind, financial institutions run that code.
- Ask HN: Examples of Unusual Code Formatting Styles?
What are some alternatives?
remacs - Rust :heart: Emacs
tinygrad - You like pytorch? You like micrograd? You love tinygrad! ❤️ [Moved to: https://github.com/tinygrad/tinygrad]
b-decoded - arthur whitney's b interpreter translated into a more traditional flavor of C
ancient-c-compilers - Very old C compilers
ZLib - A massively spiffy yet delicately unobtrusive compression library.
kdb - Companion files to kdb+ and q
boot - Build tooling for Clojure.
data_jd - Jd
teco - TECO - Text Editor and COrrector, an old classic, reimplmented in Pascal
j - j language (Ken Iverson & Roger Hui) from https:/jsoftware.com
j - various toys in j
tinygrad - You like pytorch? You like micrograd? You love tinygrad! ❤️