Just happened to be scanning the web for something on VB6 and came across this monstrosity
in [Visual Basic]
|
From: Saga on 1 Feb 2010 11:51 "MM" <kylix_is(a)yahoo.co.uk> wrote in message news:s2kam5h44p2o7nri0e7n9mpl6hjjng2n2o(a)4ax.com... > > It's about both, except I spell it .N t. > Actually, if I understood others, the idea of spelling the platform name as Nxt is so that people using a search engine and searching for the correct name will not get any unrelated hits just because people are out of topic in a nonrelated group. Regards, Saga
From: Paul Clement on 1 Feb 2010 12:42 On Mon, 1 Feb 2010 16:14:58 -0000, "Dave O." <nobody(a)nowhere.com> wrote: � > 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. That's nice but hasn't that always been the point of Visual Basic, regardless of version? It hides much of the underlying implementation from developers. Guess that makes us all "script kiddies". ;-) You could use the API function call in .NET as well, but what's the point when it can be represented in a single line of code that is self-documenting? Paul ~~~~ Microsoft MVP (Visual Basic)
From: C. Kevin Provance on 1 Feb 2010 14:40 "Saga" <antiSpam(a)nowhere.com> wrote in message news:uxmtR71oKHA.3664(a)TK2MSFTNGP04.phx.gbl... | | Actually, if I understood others, the idea of spelling the platform name as | Nxt | is so that people using a search engine and searching for the correct name | will | not get any unrelated hits just because people are out of topic in a | nonrelated | group. Regards, Saga Exactly.
From: MM on 1 Feb 2010 15:08 On Mon, 01 Feb 2010 07:54:50 -0600, Paul Clement <UseAdddressAtEndofMessage(a)swspectrum.com> wrote: >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? Why would I want to retrieve such information? I reckon in VB6 Dim i As Integer is usually a pretty good start. MM
From: MM on 1 Feb 2010 15:19
On Mon, 1 Feb 2010 16:14:58 -0000, "Dave O." <nobody(a)nowhere.com> wrote: >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. Well, of course! It's all because OOP takes the circuitous route. Here's a classic VB itinerant, seeking a pub: "I say, I say! Is there a pub near here?" Windows... "Yep, sure. Just follow this road for half a mile and you'll see it on your right." Classic VB itinerant does exactly that and is drinking his first pint of the day in no time. Now here's the OOP itinerant: SetupRepeatFrame.String = "I say" ProcessRepeatFrame.Iterations = 2 Conversation.Start SetupRepeatFrame.String = "Is there a pub near here?" ProcessRepeatFrame.Iterations = 1 Conversation.Start Windows... "Yep, sure. Just follow this road for half a mile and you'll see it on your right." OOP itinerant eventually gets there, but it's dusk by then and the pub has closed. Also, OOP ran out of memory in the meantime and has to be rebooted. MM |