chrisrink10 / mumpy Goto Github PK

Local variable names with subscripts will not be returned from a call to $NAME.

Right now, the only way to persist data is by saving off to a text file.

Right now, most syntax errors result in the parser just spitting out the first offending token. It would be great if programmers could see what their actual error is and where it occurred.

RPLY is a newer rewrite of the PLY library created by a PyPy developer for his project. It looks like it has a newer API, but may not be able to support everything that is needed for MUMPy.

Intrinsics, such as $ORDER, do not work in FOR loops. This is because they are immediately evaluated by the parser, rather than being calculated like functions and expressions.

There is actually a fourth parameter for the $PIECE intrinsic which is not presently implemented.

Right now, command scope cannot exceed the current line.

For now, programmers cannot set $ETraps to catch errors and react accordingly. Instead, they have to just live with the error condition.

The OPEN, CLOSE, and USE commands do not currently have the ability to use network devices or UNIX sockets.

Presently, the only way to loop is with GOTO commands.

M numbers in the range -1 < x < 1 should be output without a leading zero. The $JUSTIFY intrinsic is one place that this is happening, but it is probably also happening everywhere else too.

Allow programmers to access Python modules using the syntax &$funcname^module(arg1,arg2,...) or something similar.