The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
"Programming - because I'm pretty good at it, I like doing it, and have absolutely no desire to be a leader or manager. I'll help the new guys, and learn from the more experienced guys, buy you really don't want me in a position of authority, because I'm a programmer, not a politician."
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
because async / await etc are new(ish) keywords there might be code out there which has types named "async", "await" so the C# compiler does context tests for new keywords - in the example I gave some are keywords, some are types (which I omitted)
Yeah but in this case, the compiler I'm using (c#7? VS2017) bombs on that statement you gave me.
I know about contextual keywords as I've parsed C# quite a bit, and LINQ and other language additions have forced it. I've watched the keyword list in C# grow over time, and some old keywords like __stackalloc finally given life in the latest incarnations of the language
But async will break in the context you used it. I'm not sure about C# compilers before it was a keyword
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Like in Fortran IV where you can have an integer named REAL and a REAL named COMPLEX. No reserved words.
Or you could name your function SOLVE REAL PROBLEM. Spaces are ignored.
I don't know if these are still valid in modern variants of Fortran; I haven't written a single line of Fortran for 30 years.
(C.A.R Hoare, in the Fortran-77 discussions, stated "I don't know what programming languages will look like in year 2000, but they will be named 'Fortran'" - when I saw a few Fortran 2003, my immediate reaction was: He hit the nail on the head!)