5) It looks you could easily implement APL as a DSL within an existing language with an extensible parser. Racket, for instance.
I'm working on something along these lines, but not planning on keeping the APL/J-like syntax (the many meanings of juxtaposition makes parsing a line depend on the run time values attached to names). You can get more of the core idea of APL out of prop:procedure than out of extensible parsing.
Are dyads only done by putting the other operand in the string of J code? Or is there a nice way to apply a dyad to two Ruby arrays? (I wasn't sure from the Readme if this is already there or your second point in "future directions," and I'm pretty new to Ruby)
Comments
5) It looks you could easily implement APL as a DSL within an existing language with an extensible parser. Racket, for instance.
I'm working on something along these lines, but not planning on keeping the APL/J-like syntax (the many meanings of juxtaposition makes parsing a line depend on the run time values attached to names). You can get more of the core idea of APL out of prop:procedure than out of extensible parsing.
I've been doing something similar as a gem to add J commands to Ruby: https://github.com/michaelfeathers/jop
The fluent interface is likely to win because I don't want to implement hook and fork.
Are dyads only done by putting the other operand in the string of J code? Or is there a nice way to apply a dyad to two Ruby arrays? (I wasn't sure from the Readme if this is already there or your second point in "future directions," and I'm pretty new to Ruby)
No real nice way. I'm not sure where I am going to go with this, I could use a string interpolation but I'm hesitating.