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

The standart calculator don't use PEMDAS #1464

Closed
softyoda opened this issue Jan 7, 2021 · 6 comments
Closed

The standart calculator don't use PEMDAS #1464

softyoda opened this issue Jan 7, 2021 · 6 comments
Labels
duplicate Issue identified as a duplicate of another issue(s)

Comments

@softyoda
Copy link

softyoda commented Jan 7, 2021

Describe the bug
The standard calculator don't use using standard order of operations. But the scientific one work fine.

Steps To Reproduce
Make simple calculi like 1+2*3

Expected behavior

Answer should be 7 instead of 9 and the calculator should be consistent

Screenshots
image

Device and Application Information

  • OS Build:1909
  • Architecture:x64
  • Application Version:10.2011.16.0
  • Region:France
  • Dev Version Installed:No
@softyoda
Copy link
Author

softyoda commented Jan 7, 2021

@MicrosoftIssueBot
Copy link
Collaborator

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

@mdtauk
Copy link

mdtauk commented Jan 7, 2021

Switch it to the Scientific mode if you want Order of Operations by default. The standard mode performs calculations one after another.

#1212 #1436 #138

@softyoda
Copy link
Author

softyoda commented Jan 7, 2021

But is it a feature or a bug ?

@mdtauk
Copy link

mdtauk commented Jan 7, 2021

But is it a feature or a bug ?

A feature. It is a different use case and way of working.
If you need your orders of operation enforced without manually using brackets, then use the Scientific mode

@grochocki
Copy link
Contributor

Thanks for the bug report! This issue is a duplicate of #138. As discussed there, the "immediate mode" behavior in standard mode is by design, but there is a change in progress to avoid showing incorrect expressions like the one in your example (spec).

@grochocki grochocki added duplicate Issue identified as a duplicate of another issue(s) and removed triage needed labels Jan 8, 2021
@microsoft microsoft locked as resolved and limited conversation to collaborators Feb 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants