Oleg Kobchenko wrote: > > > Like Lisp and APL/J/K, they all have very simple (to parse) > langauge syntax: no precedence etc; dynamically typed; > use live objects which can mutate (as opposed to C++). > >
I dont think J syntax is easy to parse. Certainly not as easy as Scheme, for instance. Also, I asked a Ph.D in CS with emphasis on Compiler Design (who is the author of SableCC, the parser generator that is superior to ANTLR and JavaCC) about parsing J and here is what he said: http://lists.sablecc.org/pipermail/sablecc-discussion/msg00146.html Basically J is very ambiguous to parse. And the overloading of symbols for monadic and dyadic cases complicates things even more. And also, data representation in J is not parseable. A rank-90 array of shape 1 in each axis looks just like a simple scalar. But I suppose there might be some module designed for representing J data in a way that allows for easy export/import. -- View this message in context: http://www.nabble.com/squeak-tf4744740s24193.html#a13692391 Sent from the J Chat mailing list archive at Nabble.com. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
