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

7/16”+3/32” #14

Open
KirillOsenkov opened this issue Feb 7, 2018 · 3 comments
Open

7/16”+3/32” #14

KirillOsenkov opened this issue Feb 7, 2018 · 3 comments

Comments

@KirillOsenkov
Copy link
Owner

No description provided.

@VladimirRybalko
Copy link
Contributor

Hi @KirillOsenkov.
I'm aware that Quick info uses your own math parser library.
However may be we should use any external components to provide math parser.

I have some good candidates:

It allows us to avoid many existing mistakes and add a lot of new features.

What do you think?

@KirillOsenkov
Copy link
Owner Author

I like tinkering with my own stuff, NIH is strong with me :) This is also for fun and learning.

What is missing from the parser? Would you mind filing bugs at https://github.com/KirillOsenkov/MathParser/issues?

Also I haven't seen MxParser or NCalc before and I will check them out. Do you have a quick summary of what do they do better and what functionality I'm missing?

Thanks!

@KirillOsenkov
Copy link
Owner Author

I will take a look at those libraries and if they're significantly better than what I have and I won't have time to make mine catch up, then I'll certainly consider switching. But first I'd like to investigate.

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

2 participants