Just happened to be scanning the web for something on VB6 and came across this monstrosity
in [Visual Basic]
|
From: MM on 31 Jan 2010 13:11 On Sun, 31 Jan 2010 05:23:54 -0500, "Nobody" <nobody(a)nobody.com> wrote: >"MM" <kylix_is(a)yahoo.co.uk> wrote in message >news:jcham5lj914led9b0bk80su77rgbq2f0ci(a)4ax.com... >> On Sat, 30 Jan 2010 17:38:26 -0500, "Nobody" <nobody(a)nobody.com> >> wrote: >> >>>"MikeD" <nobody(a)nowhere.edu> wrote in message >>>news:O4DMcWfoKHA.1556(a)TK2MSFTNGP05.phx.gbl... >>>> He was trying to make a point...that in .NET, you have to resort to >>>> digging into many layers to get what you want....whereas in VB6, what >>>> you >>>> need is usually right there. >>> >>>That's what Imports statement is for. It opens up a dotted branch, so you >>>don't have to use the long dotted name. Kind of like not requiring that >>>you >>>type "Form1.BackColor", and just type "BackColor". >> >> You must be a .Net nut to want to take this thread further... > >Further from where? Hey, you're telling us now about the Imports statement! MM
From: Nobody on 31 Jan 2010 13:55 "MM" <kylix_is(a)yahoo.co.uk> wrote in message news:rthbm5de892itoa384u916js26ec8590di(a)4ax.com... > On Sun, 31 Jan 2010 05:23:54 -0500, "Nobody" <nobody(a)nobody.com> > wrote: > >>"MM" <kylix_is(a)yahoo.co.uk> wrote in message >>news:jcham5lj914led9b0bk80su77rgbq2f0ci(a)4ax.com... >>> On Sat, 30 Jan 2010 17:38:26 -0500, "Nobody" <nobody(a)nobody.com> >>> wrote: >>> >>>>"MikeD" <nobody(a)nowhere.edu> wrote in message >>>>news:O4DMcWfoKHA.1556(a)TK2MSFTNGP05.phx.gbl... >>>>> He was trying to make a point...that in .NET, you have to resort to >>>>> digging into many layers to get what you want....whereas in VB6, what >>>>> you >>>>> need is usually right there. >>>> >>>>That's what Imports statement is for. It opens up a dotted branch, so >>>>you >>>>don't have to use the long dotted name. Kind of like not requiring that >>>>you >>>>type "Form1.BackColor", and just type "BackColor". >>> >>> You must be a .Net nut to want to take this thread further... >> >>Further from where? > > Hey, you're telling us now about the Imports statement! Just preempting who you have invited for discussion, so the door that you have opened is closed.
From: MM on 1 Feb 2010 03:06 On Sun, 31 Jan 2010 13:55:00 -0500, "Nobody" <nobody(a)nobody.com> wrote: >"MM" <kylix_is(a)yahoo.co.uk> wrote in message >news:rthbm5de892itoa384u916js26ec8590di(a)4ax.com... >> On Sun, 31 Jan 2010 05:23:54 -0500, "Nobody" <nobody(a)nobody.com> >> wrote: >> >>>"MM" <kylix_is(a)yahoo.co.uk> wrote in message >>>news:jcham5lj914led9b0bk80su77rgbq2f0ci(a)4ax.com... >>>> On Sat, 30 Jan 2010 17:38:26 -0500, "Nobody" <nobody(a)nobody.com> >>>> wrote: >>>> >>>>>"MikeD" <nobody(a)nowhere.edu> wrote in message >>>>>news:O4DMcWfoKHA.1556(a)TK2MSFTNGP05.phx.gbl... >>>>>> He was trying to make a point...that in .NET, you have to resort to >>>>>> digging into many layers to get what you want....whereas in VB6, what >>>>>> you >>>>>> need is usually right there. >>>>> >>>>>That's what Imports statement is for. It opens up a dotted branch, so >>>>>you >>>>>don't have to use the long dotted name. Kind of like not requiring that >>>>>you >>>>>type "Form1.BackColor", and just type "BackColor". >>>> >>>> You must be a .Net nut to want to take this thread further... >>> >>>Further from where? >> >> Hey, you're telling us now about the Imports statement! > >Just preempting who you have invited for discussion, so the door that you >have opened is closed. But you could have resisted the urge to add to the thread, thus closing the door even sooner. MM
From: Paul Clement on 1 Feb 2010 08:54 On Sat, 30 Jan 2010 10:31:01 +0000, MM <kylix_is(a)yahoo.co.uk> wrote: � I was looking for a masked textbox for hex input and in the MSDN blurb � on How to Create a Numeric Text Box (.Net, naturally, this being � Microsoft) my eyes hit upon the following: � � Dim numberFormatInfo As NumberFormatInfo = � System.Globalization.CultureInfo.CurrentCulture.NumberFormat � � I mean, you REALLY have to allow that to sink in... � System.... � ....Globalization.... � ....CultureInfo.... � � ....CurrentCulture.... � � ....NumberFormat � � Yeuch! � � MM So are you saying that you would rather write an extra five to ten lines of not as readable Windows API code in Classic Visual Basic in order to retrieve this information? Paul ~~~~ Microsoft MVP (Visual Basic)
From: Dave O. on 1 Feb 2010 11:14
"Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message news:3lmdm5llsm208etrq1isniuljb8vcjlcd9(a)4ax.com... > On Sat, 30 Jan 2010 10:31:01 +0000, MM <kylix_is(a)yahoo.co.uk> wrote: > > � I was looking for a masked textbox for hex input and in the MSDN blurb > � on How to Create a Numeric Text Box (.Net, naturally, this being > � Microsoft) my eyes hit upon the following: > � > � Dim numberFormatInfo As NumberFormatInfo = > � System.Globalization.CultureInfo.CurrentCulture.NumberFormat > � > � I mean, you REALLY have to allow that to sink in... > � System.... > � ....Globalization.... > � ....CultureInfo.... > � > � ....CurrentCulture.... > � > � ....NumberFormat > � > � Yeuch! > � > � MM > > So are you saying that you would rather write an extra five to ten lines > of not as readable Windows > API code in Classic Visual Basic in order to retrieve this information? > > > Paul > ~~~~ > Microsoft MVP (Visual Basic) Well yes, and I disagree about "readability", the OOP code is just "black boxes" the script kiddie need have zero understanding of what's happening to get something that more-or-less works, all they need is to plumb the documentation to absurd depths. And yes the API is also "black boxes" to a degree, but in most cases they are very well documented black boxes so a programmer can find out exactly what's happening. Strangely in perhaps the majority of cases the OOP method is noticeably slower, this is not what I call an improvement, more one step forwards and several backwards. A few lines of VB native code with or without API calls are easier to understand what is actually happening, and far easier to modify - If you don't like how an OOP object does it's thing then in most cases you are back to the VB6 way of having to hard-code from scratch, which judging from the questions from .NETters is beyond many of them. That's not a problem if they don't pretend to be professional programmers, but regrettably.......... (you can fill in the blanks). Dave O. |