|
Mine took 45 minutes on an SSD as a Microsoft update/upgrade.
|
|
|
|
|
My upgrade came through this afternoon and I've gone from 7 to 10 and it was super simple.
I spent some time getting used to 8.1 on the laptop so the shock wouldn't be too bad when 10 arrived, but I have to say: so far I'm really, really liking Windows 10. I hoped (prayed) it would be better than 8.1 (anything is better than 8 - in fact 8 pushed me to MacOS) but I think they've recovered nicely.
Well done, Microsoft.
cheers
Chris Maunder
|
|
|
|
|
8 was a continuation of ME and Vista. Although 10 is much better, I don't like the extra spaces in Edge menus and a few other things. I do like the copy and paste for multiple sessions.
|
|
|
|
|
|
Unfortunately?
Anyways what was the point of this, being in the lounge anyway.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Is it a mistake to post it here?
If you are not interesting in something like this just skip it
modified 19-Jan-21 21:04pm.
|
|
|
|
|
0x01AA wrote: a technical discussion
Then it should be in a discussion forum.
|
|
|
|
|
Where? I will delete and move
And you organize that "Technical discussions are encouraged" disapears
modified 19-Jan-21 21:04pm.
|
|
|
|
|
The question has been posted and answered too many times already. The explanation can be found by Google if you really care.
|
|
|
|
|
|
42, half of.
Will be interesting to see whether there's any variation of results among all of these:
VS 2015, 2013, 2010, 2008, 2005, 2003, VC 6, VC 4 VC 1.5 (16-bit), GCC, cc (on iOS Yosemite downwards), Unix compilers (all flavours over the years), cc (on Linux over the years), ...
But, the big question - who will do such a test? Which of these compilers gives wrong results?
|
|
|
|
|
You are so right! But in case you have to write the Parser how you do it?
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Writing a parser - not me.
Too tough for a 50 year old educated in Mechanical Engineering
|
|
|
|
|
Avijnata wrote: Which of these compilers gives wrong results?
All the results are correct.
I can pass it through HP C and Borland C/C++
|
|
|
|
|
Thanks for this info. Still as a "Parser" it is still hard to decide
modified 19-Jan-21 21:04pm.
|
|
|
|
|
It depends on the language.
C: no expectation.
C++: no expectation.
C#: 21
Java: 21, I think?
|
|
|
|
|
C: no expectation
I think for C the case is most clear, no Operator "++" or "--" existed, so White spaces have been simply skipped.
Thanks for your Response.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Well no it's allowed, but modifying the same variable several times without sequence points in between is undefined
|
|
|
|
|
0x01AA wrote: or C the case is most clear, no Operator "++" or "--" existed Really?
|
|
|
|
|
But what is "+++" is it "+" followed by "++" or is it "++" by "+"?
Beforfe c++/c#: "- ---- --- - --x" was a correct Expression, white spaces could be ignored... only one aspect, when you Need to parse
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Everyone seems to be distracted from the real issue.
Find the moron who wrote that abomination, and leave their head on a pike outside the castle walls as a warning to others.
Software Zen: delete this;
|
|
|
|
|
"Find the moron":
Yes, I mentioned it is not of practical use. But if you write a Parser/compliler you Need to decide how to handle it
modified 19-Jan-21 21:04pm.
|
|
|
|
|
As I see it, that shouldn't be a difficult thing for a compiler. Based on operator precedence rules, evaluate the expression. There isn't any real ambiguity that you'd have to worry about, if you follow the language spec.
If you were developing a style tool, on the other hand, the tool should write the coder's resignation letter for him and leave it at that.
Software Zen: delete this;
|
|
|
|
|
Thank you very much for your Response. "There isn't any real ambiguity...".
In C: "---", "- ", " -" is ok.
In c++?
It's only a doubt from my side, to decide which way to take
modified 19-Jan-21 21:04pm.
|
|
|
|
|
0x01AA wrote: if you write a Parser/compliler
then you can simply use 42 .
|
|
|
|