-
Notifications
You must be signed in to change notification settings - Fork 156
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
No Operator between Argumant and Parentheses #170
Comments
Thank you, indeed this is a bug :-) In the version 4.3 there is no endless loop problem, it was fixed, anyway checkSyntax() should not return true. |
Please use Nuget package - this will solve the infinite loop problem. Final fix will be soon. |
thank you for your fast response dear |
fixed |
you are incredible. thank you |
dear. i updated my lib to version 4.32 |
Src was fixed, now I need to prepare maven and nuget, should be tomorrow. |
I made a present for you - Nuget package has just been published :-) Please wait 10-20 minutes - this is due to nuget indexing. Best regards |
you are best programmer ever :-* |
Now checkSyntax should return false, where checkLexSyntax should return true :-) It was w tiny bug :-) Please do not forget on repo star :-) |
you have my star from first day... |
Thank you :-) |
thank you for you dear. |
Maybe you will be interested Scalar Lite: https://play.google.com/store/apps/details?id=org.mathparser.scalar.lite I made it based on mXparser |
Please let me know if it works for you |
Its work for me dear, thank you, But about your android application, when i want to get 5 star to it, i see this app not acceptable in your country (iraq) |
I do not know the Google policy, it might that there are some legal issues to sell paid apps in Iraq :-( Please check the free versions: |
Issue title:
Issue content:
If bug/question:
i have two argumant: Salary=200,Day=2
My Expression is: Salary (Day)
checkSyntax and checkLexSyntax return true.
but is not true. no operator between salary and Parentheses
when i call calculate, it's goes to endless proceess loop
The text was updated successfully, but these errors were encountered: