Issue 25: Improve error messages
Project Member Reported by aborgabor, Jun 24, 2009
The CellHTS2 node now gives a clue where were the problem, but the actual
problem remains hidden.

It would be nice if all voidEvals would be replaced with a code like this:
RExpr e = conn.eval("try(" + command + ")");
//Check whether it is an error or not, if error report it with a meaningful
error message extracted from the expression.
Aug 21, 2009
Project Member #1 aborgabor
Fixed in version 0.4.0.
Status: Fixed
Labels: Milestone-Release0.4