Uhh... I haven't posted here in months. I come in, send, what, 8 emails? And suddenly the list is about to crack from the strain?
LOL. You are a riot. Patrick Burrows Well I sleep like a baby With the snakes and the bugs -------------------- Now Playing: depeche mode - just canīt get enough - [ -------------------- > -----Original Message----- > From: Mike C [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 28, 2002 12:19 PM > To: [EMAIL PROTECTED] > Subject: Re: VB.NET Oddity >> okay enough > > > I think back a couple of weeks ago where everyone was > slamming the Wrox guy(forget his name) about posting to the > list every time someone had a comment. > > So what is up with these two and the importance of what they > have to say to this list. I get way too many emails in a day > to have to open one up(continually) to see these two going at > it. Maybe they should exchange email addresses or better yet > phone numbers. > > L8r! > > On Tue, 28 May 2002, Brad Wilson wrote: > > > > > Patrick Burrows wrote: > > > > > No, it was converted for display according to local settings. > > > > Locale doesn't tell me whether I want to show two or four > places after the > > decimal place. Locale is only helpful for dates & times, > and when you are > > looking for very specific types of formatting (currencies, etc.). > > > > > LOL. I think of variables in terms of the information > stored in them > > > (integer = 32 bytes, for instance). Choosing to store my > 32 bytes as an > > > integer or in an array of 32 bytes doesn't make a > difference in my mind. > > > > Ignoring that it's 32 bits (not bytes), that's a > consequence of your VB > > heritage, I think. > > > > > The only reason I would choose one over the other is the > functionality > > > that data type may give me. But in C++ I can't pass my > int to a function > > > that expects an HWND. It gives me a type mismatch. Even > though it is the > > > same amount of data. > > > > Well, there are those of use who think in types, not > buckets of bits (which, > > I'll be honest, is even rather unusual for a VB > programmer). Just because an > > HWND is (opaquely) a 32-bit integer, doesn't mean that any > 32-bit integer > > can be an HWND. You can't twiddle the bits, you can't add > them together or > > subtract them, and have any meaningful answer. That's why > it's opaque. > > That's why C++ people don't store HWNDs in ints, because an > HWND is-not-a > > integer. > > > > > One that the compiler, IMO, does *not* need to be doing. > > > > After spending years in C debugging things that should've > been (and can now > > be) caught by the compiler, I don't think it's even > possible for me to > > disagree with you more on this point. > > > > > We (VB developers) develop this mentality through use of > the API and > > > translating between C++ and VB. > > > > Right. Calling the API is what causes you to think that > HWNDs are ints, when > > clearly they are not ints. They share the same amount of > data space in > > memory, and that is where the commonality begins and ends. > IMO, to treat an > > HWND as though it were truly an integer is terrible > discipline, even though > > your language forced you to declare it as one. > > > > Brad > > > > -- > > Read my web log at http://www.quality.nu/dotnetguy/ > > > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > > subscribe to other DevelopMentor lists at > http://discuss.develop.com. > > > > __________________________________________________________ > Get your FREE personalized e-mail at http://www.canada.com > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
