Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in expression evaluation ? #27

Closed
GoogleCodeExporter opened this issue Mar 22, 2015 · 1 comment
Closed

Bug in expression evaluation ? #27

GoogleCodeExporter opened this issue Mar 22, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Evaluate the expression "1+2,3" or "1,3"

What is the expected output? What do you see instead?
I would expect a syntax error, but both expressions evaluate to "3".

What version of the product are you using? On what operating system?
I am using 2.1.4 on windows 7



Original issue reported on code.google.com by hans...@gmail.com on 21 Feb 2013 at 3:36

@GoogleCodeExporter
Copy link
Author

The behaviour is deliberate. muparserx will return the result of the last 
subexpression. The last release version is lacking a feature to query the other 
values though. 

The current svn version already has support for a eval function retrieving all 
results as well as a function for querying the number of result so ýou will be 
able to handle multiple results properly by either querying their values or 
throwing an exception on your own.



Original comment by ib...@gmx.info on 23 Feb 2013 at 3:46

  • Changed state: Fixed
  • Added labels: Type-Enhancement, OpSys-All
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant