- 20,650
- 27,845
... well, it depends ...jack action said:What's wrong with simply writing:
##a \times a \times a##
There, now it's clear! No ambiguity, since multiplication is associative!

... well, it depends ...jack action said:What's wrong with simply writing:
##a \times a \times a##
There, now it's clear! No ambiguity, since multiplication is associative!
fresh_42 said:... well, it depends ...![]()
jack action said:For some reason that I don't understand, you seem to refuse recognizing the validity of those rules.
!
PeroK said:For the reason that the rules cause ambiguity. This is evidenced by the fact that the two Microsoft calculators gave different answers for the same expression.
And that 76% of the population gave the "wrong" answer.
I thought this is the principle behind national elections?micromass said:Referring to the ignorance of the total population isn't really helpful.
Krylov said:I thought this is the principle behind national elections?
micromass said:And how exactly would calculators be programmed without PEMDAS? How would the removal of PEMDAS over some other convention like white spaces by beneficial here?
Also 60% of the US population says the evolution is false or is not sure about it.
Also, this http://blog.sciencegeekgirl.com/2009/11/09/myth-because-the-astronauts-had-heavy-boots/
Referring to the ignorance of the total population isn't really helpful.
PeroK said:I'm not the only one:
http://www.math.harvard.edu/~knill/pedagogy/ambiguity/
This issue is not as clear cut as many of you would like to pretend.
No, I agree with you on this, but I have other peeves to petPeroK said:There may be more on this forum but the brow beating I've taken would deter most from uttering a word in my defence!
micromass said:Again, how would the removal of this rule be beneficial in programming?
PeroK said:I also question whether these rules help or hinder maths education - a question apparently I'm not at liberty to ask.
Its not "the brow beating" that you've taken, but that this doesn't seem to me as black and white as its being implied by this discussion. It seems to me that those rules are like Bohr's model for arithmetic. They seem important for educating children but you should get rid of them as soon as possible, i.e. when you're sure the children have the intuition about algebra(cases mentioned by micromass that imply we seem to use some rules there) that we grown ups have now.PeroK said:There may be more on this forum but the brow beating I've taken would deter most from uttering a word in my defence!
Shayan.J said:Its not "the brow beating" that you've taken, but that this doesn't seem to me as black and white as its being implied by this discussion. It seems to me that those rules are like Bohr's model for arithmetic. They seem important for educating children but you should get rid of them as soon as possible, i.e. when you're sure the children have the intuition about algebra(cases mentioned by micromass that imply we seem to use some rules there) that we grown ups have now.
You don't have to hit that with a sledgehammer like PEMDAS.micromass said:No, please do address this. I'm interested how you would teach this to children. How would you teach children to evaluate ##2p+3q##?
PeroK said:I wonder how uniformly implemented the current rules are, in any case.
I think even programmers forget most of that and just use intuition and parentheses. At least that's the case about me!Krylov said:I am tempted to say one thing specifically about programming.
In the programming languages that I know, there are many more unary and binary operators that in basic school arithmetic. (Probably C++ tops it all in this regard.) Textbooks and references usually come with a table of precedence. I found that in practice it did not at all contribute to the clarity of code when these rules of precedence were fully exploited by the programmer. Usually I found it much, much clearer when parentheses were used to remove ambiguity from complicated expressions, such as those involving both ordinary and pointer arithmetic.
Ok, now I go back to my own peeves, although I do enjoy reading along with this discussion.
I used to work in the Windows team at Microsoft, but not with the bunch that does the calculator. If I had to guess, the intent of the designers of the "four-banger" calculator, was to do simple (i.e., with two operands) add/subtract/multiply/divide calculations. I would further guess that it's stack-based, meaning that it takes the two operands and an operator (+, - *, /) and carries out the operation.PeroK said:For the reason that the rules cause ambiguity. This is evidenced by the fact that the two Microsoft calculators gave different answers for the same expression.
It wouldn't be the first time in history that 76% of the population gave the wrong answer, so I'm not impressed by that statistic.PeroK said:And that 76% of the population gave the "wrong" answer.
The expression in this article of the link seems clear-cut to me.PeroK said:I'm not the only one:
http://www.math.harvard.edu/~knill/pedagogy/ambiguity/
This issue is not as clear cut as many of you would like to pretend.
I agree, but then it wasn't a problem of ambiguity, but rather, a problem of comprehension by humans.Krylov said:In the programming languages that I know, there are many more unary and binary (and ternary) operators than in basic school arithmetic. (Probably C++ tops it all in this regard.) Textbooks and references usually come with a table of precedence. I found that in practice it did not at all contribute to the clarity of code when these rules of precedence were fully exploited by the programmer. Usually I found it much, much clearer when parentheses were used to remove ambiguity from complicated expressions, such as those involving both ordinary and pointer arithmetic.
As I have already explained, the above means exactly the same as (a + b)/(c + d). That is the purpose of the bar between the top and the bottom and the bar above the radicand in a radical. Why is this so hard?PeroK said:You don't have to hit that with a sledgehammer like PEMDAS.
I've already answered that above: the precedence of multiplication is a universal rule.
What I wouldn't do is insist on PEMDAS and then have to explain:
##\frac{a+b}{c+d}##
And why you do the additions before the division.
PeroK said:That's what I as a 15 year old would have taken exception to! I fail to see it ad a logical consequence of PEMDAS.
I think I would just treat fractions on their own merit. This is how we evaluation a fraction. There are all sorts of other things to deal with. Common factors, addition of fractions, partial fractions. Order of operations is the least of it.
PeroK said:What I wouldn't do is insist on PEMDAS and then have to explain:
##\frac{a+b}{c+d}##
And why you do the additions before the division. That's what I as a 15 year old would have taken exception to! I fail to see it ad a logical consequence of PEMDAS.
That's because you're determined to stick with PEMDAS, so you need your implied parenthesis. Whereas, I never learned PEMDAS so I'm free to say in this case we do the division last. As I have no a priori rule that operations must be done in a set order it doesn't upset my mathematic apple cartMark44 said:As I have already explained, the above means exactly the same as (a + b)/(c + d). That is the purpose of the bar between the top and the bottom and the bar above the radicand in a radical. Why is this so hard?
PeroK said:That's because you're determined to stick with PEMDAS, so you need your implied parenthesis. Whereas, I never learned PEMDAS so I'm free to say in this case we do the division last. As I have no a priori rule that operations must be done in a set order it doesn't upset my mathematic apple cart
PeroK said:I never learned PEMDAS so I'm free to say in this case we do the division last.
PeroK said:What I wouldn't do is insist on PEMDAS and then have to explain:
##\frac{a+b}{c+d}##
And why you do the additions before the division. That's what I as a 15 year old would have taken exception to! I fail to see it ad a logical consequence of PEMDAS.
A fraction implies division.jack action said:But that is a fraction, not a division. The horizontal bar adds meaning to the division implied (i.e. the parenthesis, as told by @Mark44 earlier).
Nitpicky, I know, but the thing you're talking about is an expression, not an equation.jack action said:It adds meaning to how this equation must be evaluated.
Heh, I was about to post that was one of my pet peeves.Mark44 said:Nitpicky, I know, but the thing you're talking about is an expression, not an equation.
Since you are soliciting more opinions, I agree......with @micromass and @Mark44!PeroK said:There may be more on this forum but the brow beating I've taken would deter most from uttering a word in my defence!
I don't either. I had to Google "PEMDAS" before adding my 2 cents. The rule gets converted to instinct and ultimately forgotten after a while.Shayan.J said:But I should say that I have no memory of learning the order of operations in my elementary school years. But I don't have a good memory so I can't remember how I did it!
Wait, so does this mean that we can't write binomial coefficients inline as ##n!/k!(n-k)!## ? Because ##n!/(k!(n-k)!)## looks atrocious to me. Just my two cents.Mark44 said:The expression in this article of the link seems clear-cut to me.
sophiecentaur said:Ye Gods. 184 posts. We are a grumpy lot, aren't we!
sophiecentaur said:Ye Gods. 184 posts. We are a grumpy lot, aren't we!
Greg Bernhardt said:EducatorsOmCheeto should fill this thread!
If it's written like this, no problem: ##\frac{n!}{k!(n - k)!}##, but as you wrote it the first time, it's ambiguous.TeethWhitener said:Wait, so does this mean that we can't write binomial coefficients inline as ##n!/k!(n-k)!## ? Because ##n!/(k!(n-k)!)## looks atrocious to me. Just my two cents.
IOW, 3 + 4 - 2 should be thought of as meaning (3 + 4) - 2, yielding 5. Similarly, the expression 3 - 2 + 4 should be thought of as meaning (3 - 2) + 4, again yielding 5.For expressions such as a−b+c, or a+b−c, or a−b−c, there is also a fixed convention, but rather than saying that one of addition and subtraction is always done before the other, it says that when one has a sequence of these two operations, one works from left to right: One starts with a, then adds or subtracts b, and finally adds or subtracts c.
Presumably, teachers explain that it means "Parentheses — then Exponents — then Multiplication and Division — then Addition and Subtraction", with the proviso that in the "Addition and Subtraction" step, and likewise in the "Multiplication and Division" step, one calculates from left to right. This fits the standard convention for addition and subtraction, and would provide an unambiguous interpretation for a/bc, namely, (a/b)c. But so far as I know, it is a creation of some educator, who has taken conventions in real use, and extended them to cover cases where there is no accepted convention.
[PLAIN said:https://en.wikipedia.org/wiki/Order_of_operations]Stacked[/PLAIN] exponents are applied from the top down, i.e., from right to left.[/quote]
However, both Microsoft Office Excel and Matlab R2015B evaluate 2^3^2 (i.e., ##2^{3^2}##) as if written (2^3)^2 = 64 rather than 2^(3^2) = 512.
lets imagine that we have expression as followsmicromass said:From top to bottom. What's on the top must be computed first.
PEMDAS doesn't say anything about this, since there are no other operations other than exponentiation. The convention, not always honored (see my previous post) is that the order of evaluation (the associativity) is from right to left.late347 said:lets imagine that we have expression as follows
##2^{2^{2^{2}}}##
why should it be through pemdas, that one calculates from the top right, towards bottom left?
We usually say just "base". In ##2^8##, the base is 2 and the exponent is 8.late347 said:Are you supposed to initially judge that the leftmost number at the bottom, two = "the base number". Therefore, essentially, all the others two's are some sort of powers as themselves. I suppose it makes sense like that. Is that a real math term anyway "base number"?
late347 said:Usually people simply speak 2 squared (for the case of ##2^2##. And not e.g. 2 as the base number, and 2 as the exponent.
I'm not a botanist, but I took one field botany class many years ago, purely for interest, and have managed to hold onto the scientific names of quite a few plants. I've noticed that the scientific names of several plants have changed, including that or Oregon grape, a shrubby plant that grows in my area. It used to be Berberus aquifolium, but now it's Mahonia aquifolium, so they changed the genus the plant belongs to.OmCheeto said:More recently:
Om; "Who and when was it decided to change the Latin name of the "Guppy"? I learned that when I was 7, and now I see it's been changed."
Botanists; "We did".
Om; "When"?
Botanists; "Um..."
Om; "And why"?
Botanists; "Well..."
Sure, but I imagine that if most mathematicians or scientists saw ##n!/k!(n-k)!## in a paper, they'd probably automatically associate it with a binomial coefficient immediately, rather than thinking it meansMark44 said:If it's written like this, no problem: n!k!(n−k)!\frac{n!}{k!(n - k)!}, but as you wrote it the first time, it's ambiguous.
Probably so, but if this appeared in a paper, it would likely be nicely formatted as ##\frac{n!}{(n - k)! k!}##.TeethWhitener said:Sure, but I imagine that if most mathematicians or scientists saw ##n!/k!(n-k)!## in a paper, they'd probably automatically associate it with a binomial coefficient immediately, rather than thinking it means
$$\frac{n!(n-k)!}{k!}$$
Image source: at 02:30
micromass said:That and the date convention. How does 3/1/15 for 1 march 2015 make logical sense... at all?
Ben Niehoff said:Because we actually say "March 1st, 2015"
Ben Niehoff said:"March 1st, 2015", not "1 March 2015".
When asked for my birth date, I reply, "Six March forty-seven."micromass said:no logical reason to say it like that.
Bystander said:When asked for my birth date, I reply, "Six March forty-seven."