3 ms·
I spent most of a Saturday morning picking apart the prototype J interpreter (http://www.nsl.com/papers/origins.htm http://www.nsl.com/papers/origins.htm) with
by silentbicycle 16y ago
I spent most of a Saturday morning picking apart the prototype J interpreter (http://www.nsl.com/papers/origins.htm http://www.nsl.com/papers/origins.htm) with GDB, which convinced me there was something deep there.
I've read most of _J for C Programmers_, and, this week, I also got _APL: An Interactive Approach_. The mindset is starting to make a lot of sense. (I've also looked at A+, but I'd rather stick to the ASCII variants.)
- chl 16y agoA+ has an ASCII mode, activate w/: $mode ascii For a mapping between ASCII tokens and APL glyphs, see: - http://www.vector.org.uk/aflat/tutor/index.htm http://www.vector.org.uk/aflat/tutor/index.htm - http://www.aplusdev.org/APlusRefV2_15.html#HEADING349 http://www.aplusdev.org/APlusRefV2_15.html#HEADING349
- silentbicycle 16y agoGood to know, thanks. I will give A+ another look. Having read more about APL, though, I'm feeling less inclined to write off the extended character setup. Still, it's an issue one needs to sort out upfront. I guess it's the APL equivalent of bitching about parenthesis, when either is a shallow detail compared to what's really novel about the languages. Many languages seem to have shibboleth complaints, to show when people haven't made it past the surface - Lua indexes from 1, Lisp has the parens, Python has the whitespace, etc. Maybe there's a community value in that, I don't know.