I spotted a typo in your blog post. When you start talking about code on pizza boxes, you can read “Anyway, writing code by hand is very due for a serious experimentation.”, there's something missing between "very" and "due" :)
446 karma · joined March 3, 2021
I spotted a typo in your blog post. When you start talking about code on pizza boxes, you can read “Anyway, writing code by hand is very due for a serious experimentation.”, there's something missing between "very" and "due" :)
For this particular series, I have _no idea_ how many articles it will take to cover enough APL syntax for me to be satisfied with the state of the interpreter. This is mostly a hobby project to help me learn APL and to help me learn about interpreters and related materials, so I feel the need to write about every major step I take, which might actually look like a minor step from the point of view of number of features that get added.
Does my reply make sense?
Something that's bothering me is your pairing of "symbolic" and "APL". As far as my (limited) knowledge goes, symbolic languages are those like Mathematica, where you can perform symbolic substitutions, for example. APL is not symbolic, it only uses "weird" characters as its primitives (its built-in functions).
I don't know if your wording is too amateurish because you are using lingo outside of my knowledge. Does "make use of the speed of array-based language, but save computation time by compiling" refer to using an array language that is compiled? [Co-dfns](https://github.com/co-dfns/co-dfns) compiles a dialect of APL, so that might be interesting to you.
Feel free to ask any questions you might have in here or in the comments of the blog articles.
The series is not complete yet but rest assured that I haven't given up on it :)