j-incunabulum
kcc
j-incunabulum | kcc | |
---|---|---|
2 | 1 | |
33 | 180 | |
- | 0.0% | |
0.0 | 10.0 | |
over 10 years ago | over 1 year ago | |
C | ||
- | MIT License |
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.
j-incunabulum
- Origins of J
-
An Implementation of J – Incunabulum
The code won't compile on modern C compilers due to some antiquated syntax. https://github.com/tangentstorm/j-incunabulum has a translation that should work on modern compilers.
The original code is worth investigating if you're into CS archeology. J is as interesting of a language as Lisp and I was amazed by the tiny implementation. However, the original code is buggy and will crash on slightly malformed input.
kcc
-
Origins of J
true. only k is faster, easier to learn, and does the trick :)
that said, i hold the view that mastering programming in an ultra-high level language such as APL or k does not absolve a computer programmer from learning lingua franca of our trade, which is due to k&r, will stay around for a very long time, and is called C.
people who don’t know c are ok, only they are not involved in computer programming. their field is known as software development. feel the difference.
i once attempted to convey my own understanding of this divide in a chapter titled “no stinking loops”, which is a nod to Apter’s mandatory nsl.com:
https://github.com/kparc/kcc#no-stinking-loops
What are some alternatives?
ooj - the origins of J
altc - scaffolding for my c projects