 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C# / September 2007Double vs double
Is there a difference between: private Double[,] B = new double[2, 2]; and private double[,] E = new double[2, 2]; The editor shows the Double in aqua and double in blue leading me to think so. But the screen tip indicates they are equivalent. mr peanut, No, there isn't. double (lower case) is nothing more than a C# alias for System.Double, which is the type included in MSCORLIB. They are the same thing.  Signature- Nicholas Paldino [.NET/C# MVP] - mvp@spam.guard.caspershouse.com > Is there a difference between: > private Double[,] B = new double[2, 2]; [quoted text clipped - 3 lines] > The editor shows the Double in aqua and double in blue leading me to think > so. But the screen tip indicates they are equivalent. But are they the same across all platforms? For example, if I was to declare a variable as an "int" on a 32 bit OS the size of it will be 32 bits, but if I was to use the "int" keyword on a 64 bit OS, will it reference a 32 bit integer or a 64 bit integer? Just curious, thanks. It will be a 32 bit integer. The type is consistent across platforms. Signature- Nicholas Paldino [.NET/C# MVP] - mvp@spam.guard.caspershouse.com > But are they the same across all platforms? > [quoted text clipped - 3 lines] > > Just curious, thanks. Thanks Guys, OK, I guess the one thing that may not be the same is that different programming languages may map the same keyword to a different CLR type. For example, perhaps Cobol.Net (or whatever) could map the keyword "int" to System.Int64 rather than to System.Int32. I realize that this observation is beyond the scope of the posters question but I just wanted to point it out, I remember reading somewhere someone suggesting to use the CLR type names rather than the aliases for a couple of reasons and I think one of the was what I mentioned above. In other words, using the CLR type names is supposed to be better for clarity (even for people coming form different programming languages) although I believe Microsoft like us to use the aliases better. Cheers. > It will be a 32 bit integer. The type is consistent across platforms. > [quoted text clipped - 5 lines] >> >> Just curious, thanks. C# actually defines what an int is (32-bit signed integer). C++ and C don't, and it is up to the particular compiler implementation to define them. > -----Original Message----- > From: Rene [mailto:a@b.com] [quoted text clipped - 41 lines] > >> > >> Just curious, thanks. > OK, I guess the one thing that may not be the same is that different > programming languages may map the same keyword to a different CLR type. [quoted text clipped - 10 lines] > clarity (even for people coming form different programming languages) > although I believe Microsoft like us to use the aliases better. Different programming languages has completely different data types. Cobol has data types like: 01 NUMBER-1 PIC 9(6) PACKED-DECIMAL. 01 NUMBER-2 PIC 9(6) PACKED-DECIMAL. 01 RESULT PIC 9(6) DISPLAY. 01 V PIC 9(4)V99 DISPLAY. 01 VV PIC ZZZ9.99 DISPLAY. 01 POS PIC S9(4) DISPLAY VALUE 12. 01 NEG PIC S9(4) DISPLAY VALUE -12. 01 S PIC X(10). 01 S2 PIC XX. I think they will have bigger problems than int versus int32. Arne > OK, I guess the one thing that may not be the same is that different > programming languages may map the same keyword to a different CLR type. [quoted text clipped - 6 lines] > suggesting to use the CLR type names rather than the aliases for a couple of > reasons and I think one of the was what I mentioned above. That's a good reason to use CLR names in method names - ReadInt32, ReadInt64 etc. It's not a good reason to > In other words, using the CLR type names is supposed to be better for > clarity (even for people coming form different programming languages) > although I believe Microsoft like us to use the aliases better. People who are reading/writing C# should learn C# - trying to make code readable for non-C# programmers seems like a non-starter to me, especially as it's likely to make the code *less* readable for C# coders (who in most cases are likely to be the bulk of the readership). SignatureJon Skeet - <skeet@pobox.com> http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet If replying to the group, please do not mail me too > But are they the same across all platforms? > > For example, if I was to declare a variable as an "int" on a 32 bit OS the > size of it will be 32 bits, but if I was to use the "int" keyword on a 64 > bit OS, will it reference a 32 bit integer or a 64 bit integer? It will still be 32 bit on a 64 bit platform. The only type that changes size is IntPtr. Arne Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.