💡𝚂𝗆𝖺𝗋𝗍𝗆𝖺𝗇 𝙰𝗉𝗉𝗌📱

  • 242 Posts
  • 601 Comments
Joined 7 months ago
cake
Cake day: November 25th, 2023

help-circle































  • The rules and the acronyms describe different things.

    No, they don’t.

    If you have to make more rules to say M and D are the same,

    I didn’t make more rules - that’s the existing rules. Here’s one of many graphics on the topic which are easy to find on the internet…

    …that’s one of the two examples you used?

    Yes. Did you try looking for one and ramping it up to the most difficult level? I’m guessing not.

    IT IS AMBIGUOUS IN THIS POST

    No, it isn’t. Division before subtraction, always.

    ALL EXAMPLES I HAVE SHOWN

    None of those have been ambiguous either, as I have pointed out.

    That is the problem at hand.

    The problem is people not obeying the rules of Maths.

    There is no real problem solving in trying to decipher poorly written shit

    It’s not poorly written. It’s written the exact way you’d find it in any Maths textbook.


  • You are adding more rules

    I’m stating the existing rules.

    If all that matters is higher orders first

    I don’t even know what you mean by that. We have the acronyms as a reminder of the rules, as I already said.

    I know operators apply to the numbers to their right.

    If you know that then how did you get 2-2+2=-2?

    With 2/22, you don’t know if it is 22/2, or 2/(2*2)

    Yes you do - left associativity. i.e. there’s no brackets.

    When you are dividing by numbers, you put them all in the denominator

    Only the first term following a division goes in the denominator - left associativity.

    BY CONVENTION, as I said. You don’t have to repeat what I said a second time.

    I didn’t. You said it was a convention, and I corrected you that it’s a rule.

    It’s not like you could have tried in your head different orders to combine 3 numbers.

    addition first

    2-2+2=4-2=2

    subtraction first

    2-2+2=-2+2+2=-2+4=2

    left to right

    2-2+2=0+2=2

    3 different orders, all the same answer



  • Still not quite sure what the different design ideas behind Xamarin and Maui is

    Xamarin had separate projects for each platform, whereas they’re all together in MAUI. Also Xamarin was tied to .NET Standard 2.1, whereas MAUI uses the latest .NET releases (starting with 5 or 6 - I’m now on 8). MAUI major releases now come out at the same time as Visual Studio updates. Also, as mentioned, MAUI uses handlers, but I’m still trying to work out how you actually use one to create a property (sigh). There was a few, annoying, breaking changes too. e.g. in Xamarin I could define the span and height of an element in a Grid with a single command, but now I have to use two (for some bizarre reason setting the column span is now entirely separate. I ended up writing my own function so I could do it all in 1 line again).



  • Multiplication comes before division in some forms, like PEMDAS. In the example I use, this changes the answer

    If you have both multiplication and division then you do them left to right. PEMDAS doesn’t mean multiplication first, nor does BEDMAS mean division first. It’s PE(MD)(AS) and BE(DM)(AS) where the bracketed parts are done left to right.

    you should specify what it is operating on

    Left associativity means it always operates on the following term. i.e. terms are associated with the sign on their left.

    The minus sign only applies to the middle term, by convention

    By the rule of left associativity.

    But if you use one of these acronyms, you end with this expression evaluating to -2

    No it doesn’t. How on Earth did you manage to get -2?

    all these acronyms end up being useless waste of time

    No they’re not, but I don’t know yet where you’re going wrong with them without seeing your working out.