[mlochbaum]

> J can actually be parsed

Don't know where you got that one. J source can't even be tokenized except during execution!

  NB. Compute n from reading a file of something
  n : 0
    Is this the source of a function, or a string?
  )

Besides that, J has the same contextful issues as APL with regards to the value of variables determining how the syntax fits together. It's missing a few dark corners like niladic functions, but these are small differences; it's still fundamentally unparseable.

[rscho]

Regarding that, I am surprised that a 'more limited APL' lacking this ambiguity and opening the way to easy compilation never appeared (to my knowledge). I essentially use J for data wrangling and pretty much never use the metaprogramming features of the language (". and the like). An 'APL NumPy' would be quite nice, IMO.

[beagle3]

K can be parsed. Even Q (the English version of K) can be parsed if you consider the prelude a part of the language (rather than part of the runtime environment).