On Mon, 27 May 2002 22:36:37 -0400, Mark Burns <[EMAIL PROTECTED]> wrote:
>Tell me, does this tell you _anything at all_ about this new "Visual
Basic"?
>(remember that the first word in Basic is supposed to be "Beginners'"?)
How
>in the heck is a real, actual BEGINNER supposed to cope with nuance
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 -
Patrick,
Thanks, I think this is the sort of insight I was looking for.
I'll shut up and resume lurking mode as soon as I correct one
mis-interpretation I've left hanging out there on this subject.
Yes, I did use the term "Beginner, but I really didn't mean "true
beginners" in the first-time writ
>
> 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 fo
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
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, e
> > I can't think of a logical reason why the guy who wrote the Format()
> > function would do this. In fact, I would think it would be best to
> > convert anything passed in, no matter what, into a string, do the
> > formatting (which is now easier cause it is a string) and
> then return
> > the
Patrick Burrows wrote:
> I can't think of a logical reason why the guy who wrote the Format()
> function would do this. In fact, I would think it would be best to
> convert anything passed in, no matter what, into a string, do the
> formatting (which is now easier cause it is a string) and then r
> > 1 - What's new is that the behaviour is different to VB6.
>
> OK, the specific issue is, but the broader issue of implicit
> conversion subtleties, especially with dates, is not new at all.
> Although different, I think VB.NET's (and the CLR's) tighter type
> enforcement will prevent more bug
> His point is that if experienced developers make these sorts of
> mistakes, then what hope do beginners have - however I would contend
> that this sample is only a mistake that "legacy" VB'ers would
> make, not
> newbies.
Exactly.
Patrick--I'll show you legacy--Burrows
Patrick Burrows
Pol
, 27 May 2002 11:57:31 +1000, Michael Weinhardt
> > <[EMAIL PROTECTED]> wrote:
> >
> > >Hi Patrick,
> > >
> > >I think the Format function considers "1:00" to be a string and
> > subsequently can't match with the formatting defined by &quo
The Format$() function in VB6 accepted strings as arguments and returned
strings as a result. Yes, it could also return dates, or numbers, or
whatever else. And it could also accept all those values.
Frankly, it never occurred to me that in VB6 the value I passed in would
be first coerced into t
> 1 - What's new is that the behaviour is different to VB6.
OK, the specific issue is, but the broader issue of implicit
conversion subtleties, especially with dates, is not new at all.
Although different, I think VB.NET's (and the CLR's) tighter type
enforcement will prevent more bugs than it ca
ction - instead you have to use the
.ToString() of each object which is much safer.
-Original Message-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Mark Burns
Sent: Tuesday, 28 May 2002 14:37
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] VB.NET Oddity
Patrick,
Uhm...You are
essage-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Steve Johnson
Sent: Tuesday, 28 May 2002 14:47
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] VB.NET Oddity
> ...and even you would "never have thought of that" in regards to
> something seemingly simple and
> ...and even you would "never have thought of that" in regards to
> something
> seemingly simple and relatively inocuous in this new VB.Net?...
Uhhh...
1 - What's new about this?
2 - What the heck does this have to do with VB vs. other languages? I
can't think of a date class or API that rea
;Format(CDate("1:00"), "hh:mm tt")
> >
> >cheers,
> >mw
> >
> >> -Original Message-
> >> From: Patrick Burrows [mailto:[EMAIL PROTECTED]]
> >> Sent: Monday, 27 May 2002 11:53 AM
> >> To: [EMAIL PROTECTED
-
>> From: Patrick Burrows [mailto:[EMAIL PROTECTED]]
>> Sent: Monday, 27 May 2002 11:53 AM
>> To: [EMAIL PROTECTED]
>> Subject: [DOTNET] VB.NET Oddity
>>
>>
>> Can anyone explain to me these results in VB.NET:
>>
>> ?Format("1:00", &q
: Patrick Burrows [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 27 May 2002 11:53 AM
> To: [EMAIL PROTECTED]
> Subject: [DOTNET] VB.NET Oddity
>
>
> Can anyone explain to me these results in VB.NET:
>
> ?Format("1:00", "hh:mm tt")
> "hh:mm tt"
>
Can anyone explain to me these results in VB.NET:
?Format("1:00", "hh:mm tt")
"hh:mm tt"
I am expecting it to be "1:00 am"
I can get named formats to work ("Medium Time") but not any custom formats.
What am I missing?
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
20 matches
Mail list logo
