3 ms·
I found the APL papers interesting, too. Unfortunately, without the corresponding source code available, it is--at least for me--increasingly difficult to make
by sb 16y ago
I found the APL papers interesting, too. Unfortunately, without the corresponding source code available, it is--at least for me--increasingly difficult to make sense of the APL papers and I am not sure/convinced this has anything to do with changed nomenclature. (For example, AFAIR, I don't really see inline caching in the description of "A Software High Performance Interpreter" by Saal and Weiss 1974.)
- silentbicycle 16y agoThe APL literature seems to be pretty insular, including terminology. I've been investigating it as a fascinated outsider. Tim Budd's _An APL Compiler_ (http://web.engr.oregonstate.edu/~budd/Books/aplc/ http://web.engr.oregonstate.edu/~budd/Books/aplc/) covers some issues, but goes into much less depth than I hoped. That page has the source accompanying the book, though. This guy's site (http://home.earthlink.net/~swsirlin/apl.html http://home.earthlink.net/~swsirlin/apl.html) has some further thoughts loosely based on that book and its compiler.
- sb 16y agoThe APL literature seems to be pretty insular, including terminology. I could not agree more, honestly! I think my route towards understanding some of the optimizations based on the current implementation of J and/or NARS2k (http://www.nars2000.org/ http://www.nars2000.org/), probably this is the route to enlightenment. Before embarking on that journey, I will read up on your hints, thank you very much!
- silentbicycle 16y agoIf you want to continue this discussion, my contact info is in my profile. Take care.