You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Run latest sample from svn.
2. Enter expression "void = 15" (without "").
3. See the result.
What is the expected output? What do you see instead?
I expect that "void" cannot be used as name for variable, because "void" is
ToString() output of variables with type VOID.
The above expression is instead true and 15 is assigned to void.
Original issue reported on code.google.com by Rotter.M...@gmail.com on 16 Apr 2013 at 6:58
The text was updated successfully, but these errors were encountered:
"void" is not a keyword in muparserx at the moment. I don't see the need to act
preemptively. A variable named "void" does work in every aspect of muparserx so
there are no real problems with naming a variable "void".
Original comment by ib...@gmx.info on 16 Apr 2013 at 3:47
Sorry, I don't want to have it banned at least not for now. "void" is currently
not a keyword in muparserx and the only reason for banning certain names should
be to avoid collisions with keywords. Too many tests and checks will interfere
with the useability especially if there they impose artificial restrictions.
Original comment by ib...@gmx.info on 16 Apr 2013 at 4:17
Original issue reported on code.google.com by
Rotter.M...@gmail.com
on 16 Apr 2013 at 6:58The text was updated successfully, but these errors were encountered: