|
It does. This is not a new independent building, but a new wing. The elevators in the old wings go 4, 3, 2, 1, U - the U is for "underetasje", or "sub-floor". (For buildings having two basement levels, it is common to label them U1 and U2.)
I guess that the reason why they changed it is that we have a large fraction of foreign employees who don't speak Norwegian, so the management (or elevator constructor?) wanted something language independent. You could say that "U" indicateds "underground", but even an English based abbreviation is sort of language dependent . Sure, almost everybody around has at least some understanding of English, but sometimes very little and limited to professional job terms; in the elevator their mind is never tuned in to English. A U is about as good as a Chinese ideograph - just some blurb that makes little sense except symbolizing the basement level.
|
|
|
|
|
Lopatir wrote: who counts anything from zero?
Err...computer scientists do. Because it isn't a count, but a pointer.
|
|
|
|
|
Lopatir wrote: who counts anything from zero?
Everybody, but many don't realize it. Zero is a perfectly good value for counting. For instance, there are zero elephants in this room.
Whenever you count something you always start with zero, then you count the first item as one. It's just so intuitive, you don't really think about it.
|
|
|
|
|
CodeWraith wrote:
Variants, anybody?
they're called "var", in C#
|
|
|
|
|
They are not the same thing, but I still don't like them at all. I prefer code that's readable without the help of costly tools like Visual Studio or Intellisense.
|
|
|
|
|
|
Quote: costly tools like Visual Studio or Intellisense. I use the community edition of VS 2015 at home for free and it has intellisense built it for free.
Did I mention it was free? Not costly at all.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Don't call Rome just yet. The Microsofties may all be absolutely selfless may have performed enough miracles, but they have to be dead to be made saints by the Pope.
Personally, I have already moved on and would not want to invest any time or money in Microsoft anymore. There are far more interesting things to do than keeping up with their escapades.
|
|
|
|
|
No, they're called dynamic in C#.
Using var , your variable is still strongly-typed; you're just letting the compiler work out what that type is.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Oh, you mean boxing? Because that is exactly what VARIANT does in COM and VB....
|
|
|
|
|
|
Now we must talk about the Oracle at Delphi. Sheesh....
|
|
|
|
|
|
I'm just glad Delphi wasn't at (from) Oracle.
|
|
|
|
|
I just mentioned that, before reading your post.
|
|
|
|
|
which means ... we are both correct - that's great
Regards,
|
|
|
|
|
Yeah. I was wondering what Anders would say about VB being C#'s progenitor.
|
|
|
|
|
Applause ! Finally Delphi is mentioned.
And, can we not give Anders, Mads, Eric L., Eric T., and others, some credit for bring geniuses who created something remarkable ?
«Differences between Big-Endians, who broke eggs at the larger end, and Little-Endians gave rise to six rebellions: one Emperor lost his life, another his crown. The Lilliputian religion says an egg should be broken on the convenient end, which is now interpreted by the Lilliputians as the smaller end. Big-Endians gained favor in Blefuscu.» J. Swift, 'Gulliver's Travels,' 1726CE
|
|
|
|
|
|
Was happy that they finally updated the switch in C# to have be as flexible as the Visual Basic Select Case. Waited a long time for that one.
|
|
|
|
|
|
Well your certainly have the right to not use the new features. How about something about why you do not like the changes to the switch statement.
|
|
|
|
|
One of the "beauties" of the stock C# switch statement was that using integer case qualifiers it compiled to a mean and lean jump-table in CIL. I assume it still does; have yet to see any performance comparisons of use of the new features and other techniques for switch-a-roo.
I like the new features.
«Differences between Big-Endians, who broke eggs at the larger end, and Little-Endians gave rise to six rebellions: one Emperor lost his life, another his crown. The Lilliputian religion says an egg should be broken on the convenient end, which is now interpreted by the Lilliputians as the smaller end. Big-Endians gained favor in Blefuscu.» J. Swift, 'Gulliver's Travels,' 1726CE
|
|
|
|
|
Note that this is not at all set by the language defintion, but 100% decided by the compiler writer. I have seen compilers (not C#) that generate completely different code depending on the optimization switches: If you optimize for speed, and the case alternatives are sparse, you may end up with a huge jump table. If you optimize for code size and the number of specific cases is small, it might compile like an if ... elseif ... elseif ... When you switch on strings, hash methods are sometimes used to reduce the number of string comparisons that must be done.
Compilers may try out several different methods of compiling a switch statements, and assign scores to each alternative based on the compiler options, such as optimization and target architecture. The one with the highest score wins, and is passed on to later compiler stages. This sure slows down compilation, but is generally worth it.
A small sidetrack, but closely related: Contrary to common belief, modern standards for sound and image processing, such as MP3 and JPEG, does not specify how the compression is to be done, only how a compressed file is decompressed. A good compressor may try out a handful of different ways to compress the original (sometimes varying wildly in compressed encoding), decompress according to the standard and do a diff with the source material. The alternative with the smallest diff result is selected. (Or, the size of the diff result gives that alternative fewer or more points on the scoreboard, together with e.g. compressed size). The compress-decompress-diff-evaluate sure takes CPU power, but today we have plenty of that, at least for sound and still images.
|
|
|
|
|
I think that is the reason that it took so long to upgrade the switch statement. I would expect that you are right an it still with do that. Of course could also do a string which would be a little more complex, and I am sure there is a different implementation for a int and string. swtich statements are a bad smell, so I look to see if there is a better implementation than a swtich.
|
|
|
|
|