A twist of lemon
I was browsing the archive of design notes from the early days of the C# language the other day. Apparently whoever was editing the notes back then had a sense of humour. (UPDATE: It was Scott, just as I suspected.) I stumbled across this note from May 1999:
We considered a proposal to rename short, int, and long to short, tall, and grande. More thought on this issue is required; we will revisit this issue on Friday.
And yet the notes for the following Friday say nothing of it. Someone dropped the ball.
It’s not too late. I propose in the same vein that we rename float, double and decimal to singleshot, doubleshot and quadrupleshot. byte can be cappuccino. And of course the BigInteger in the new math library can be half double decaffeinated half-caf with a twist of lemon.
Comments
Anonymous
February 14, 2010
I think byte should be <b>Chocolate Covered Espresso Bean</b>Anonymous
February 14, 2010
As long as you rename Nullable as Decaf, sure.Anonymous
February 14, 2010
... and wouldn't this make C# look even more like Java? Badoom-tsh! Someone had to say it.Anonymous
February 14, 2010
This post is crying out for a Cup<T> joke, but I can't think of one that fits, dagnabbit.Anonymous
February 15, 2010
You have to fit the waka waka gruntie three-quarter plasma no salt bundahoo somewhere. http://ars.userfriendly.org/cartoons/?id=20081202Anonymous
February 15, 2010
Didn't you notice float is already named after a coffee drink?Anonymous
February 15, 2010
The comment has been removedAnonymous
February 15, 2010
So the unsigned integers would be ushort, utall and ugrande? ufat! uugly!Anonymous
February 15, 2010
Such a pity this didn't get in. It could easily be that killer feature that'd get Java programmers to migrate in droves!Anonymous
February 15, 2010
Why not single, double, and a martini?Anonymous
February 15, 2010
If byte is a cappuccino, the I guess a bit is an espresso?Anonymous
February 15, 2010
byte should be an espresso, sbyte would then be a machiato. Nulllable<T> would be a coffee sleeve char would be a chaiTeaLatte IntPtr would be a Corretto As benefits decimal's secretive, not really a primitive at all status I propose it to be a decaffAnonymous
February 15, 2010
try { tall id = tall.Parse(idInput) quadrupleshot salary = quadrupleshot.Parse(salaryInput); Foo(id, salary); } catch (Frappuccino frap) { serve frap; }Anonymous
February 15, 2010
Fredrik: http://blogs.msdn.com/ericgu/576679.aspx#577019Anonymous
February 15, 2010
There she was just a-walkin' down the street, singin' "Do wah diddy diddy dum diddy do" Snappin' her fingers and shufflin' her feet, singin' "Do wah diddy diddy dum diddy do" She looked good (looked good), she looked fine (looked fine) She looked good, she looked fine and I nearly lost my mindAnonymous
February 15, 2010
So it finally happens that C# comes in different flavorsAnonymous
February 15, 2010
how about: Small , big and OMG?Anonymous
February 15, 2010
Why only address the number types? Let's solve the big problem and make the language skinnable. Now you can have C# look like C, Java, Assembler, or Malbolge. You can have Easter, Halloween, and Christmas skins. You can download the .NET 5.0 skin before the release of .NET 4.0. This would really open the door to a world of unlimited possibilities.Anonymous
February 16, 2010
How about Hobbit, Orc and Troll?Anonymous
February 16, 2010
@Daniel Common Lisp can only be invented once, unfortunately. You've got to love reader macros... As a side note, writing an IDE with code completion for that would sure be fun!Anonymous
February 16, 2010
I kinda woulda been ok with the exceedingly-boring bool, char, int8, int16, int32, int64, float32, float64. I'm sure types like byte, short, int, long, float, and double make some programmers feel right snuggly and warm as if they were home at last, but the sense of security backfires the first time you try to match native code's LONG against c#'s long in a P/Invoke signature. And trying to explain to a non-C developer what a double is a double of, and what a long is longer than, and what a short is shorter than. Floats and ints are tricky enough already. No need for coffee to add to the confusion.Anonymous
February 17, 2010
@Doug - Upvote. I agree int8, int16, etc. would have been better and clearer. Why over-complicate things with short and long.Anonymous
February 17, 2010
I think I saw in F# that all data types are going away anyway... Maybe step one is change them all to int∞ And eventually just Object, or was it Variant?Anonymous
February 17, 2010
The comment has been removedAnonymous
February 17, 2010
How about these renamings: float -> not_suitable_for_monetary_arithmetic double -> still_not_suitable_for_monetary_arithmetic