Re: VB.Net Rules!
I disagree.
VB6 is not slightly more verbose.
VB6 is _HALF_ the verbosity
I mean all the crap for events; I mean fuck VB DOTNET
Re:
VB6 was a bit less verbose than VB.NET because it contained less
features. For example VB.NET is fully object oriented, which of
course
adds a whole bunch of new keywords.
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
why is it that 80% of vb6 programmers 'never built a class' but MS
held us down against our will and forced classes into our mouths?
I was RAPED BY MICROSOFT; WE SAID NO,NO,NO
AND NO MEANS NO
I WAS RAPED BY MICROSOFT AND I REFUSE TO SIT IDLY BY WHILE THEY SIT
THERE AND INVENT A NEW DIALECT OF VISUAL FRED
On Feb 18, 6:42 am, Göran Andersson <g...@guffa.com wrote:
I disagree.
VB6 is not slightly more verbose.
VB6 is _HALF_ the verbosity
I mean all the crap for events; I mean fuck VB DOTNET
Re:
VB6 was a bit less verbose than VB.NET because it contained less
features. For example VB.NET is fully object oriented, which of
course
adds a whole bunch of new keywords.
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
VB6 _WAS_FULLY_OBJE CT_ORIENTED_ENO UGH_BUT_NOBODY_ USED_IT_
why is it that 80% of vb6 programmers 'never built a class' but MS
held us down against our will and forced classes into our mouths?
I was RAPED BY MICROSOFT; WE SAID NO,NO,NO
AND NO MEANS NO
I WAS RAPED BY MICROSOFT AND I REFUSE TO SIT IDLY BY WHILE THEY SIT
THERE AND INVENT A NEW DIALECT OF VISUAL FRED
On Feb 18, 6:42 am, Göran Andersson <g...@guffa.com wrote:
pfc_s...@hotmai l.com wrote:
>
Yes, the only solution to make VB.NET less verbose is to make it not
BASIC. ;)
>
As VB.NET is BASIC with added features like type safety and object
orientation, it gets verbose. Most features are added by adding keywords
to existing commands.
>
Take for example the Dim command. In the original form it was only used
to create arrays by specify their dimensions (hence the name):
>
DIM A(4)
>
Regular variables would not be declared at all, just created when used.
To allow for explicit declaring of varibles, the DIM command was altered
to also allow for declaring regular variables:
>
Dim B$
>
To add type safety, the As keyword was added to the command:
>
Dim B as String
>
Similar ways of adding keywords can be seen througout the language.
>
>
VB6 was a bit less verbose than VB.NET because it contained less
features. For example VB.NET is fully object oriented, which of course
adds a whole bunch of new keywords.
>
>
>
Sadly you have no choise in the long run. VB6 is replaced by VB.NET, so
MS will drop the support for it entirely in a few years.
>
>
>
>
>
>
>
--
Göran Andersson
_____http://www.guffa.com
so.. c# is the solution to VB.net code verbosity?
Yes, the only solution to make VB.NET less verbose is to make it not
BASIC. ;)
>
As VB.NET is BASIC with added features like type safety and object
orientation, it gets verbose. Most features are added by adding keywords
to existing commands.
>
Take for example the Dim command. In the original form it was only used
to create arrays by specify their dimensions (hence the name):
>
DIM A(4)
>
Regular variables would not be declared at all, just created when used.
To allow for explicit declaring of varibles, the DIM command was altered
to also allow for declaring regular variables:
>
Dim B$
>
To add type safety, the As keyword was added to the command:
>
Dim B as String
>
Similar ways of adding keywords can be seen througout the language.
>
I thought that VB6 was.
VB6 was a bit less verbose than VB.NET because it contained less
features. For example VB.NET is fully object oriented, which of course
adds a whole bunch of new keywords.
>
I am not going to embrace dotnet until the next version; I've been
saying that for several releases now.
saying that for several releases now.
I just can't deal with a bloated IDE that crashes on me.
I refuse to do it.
I refuse to do it.
Sadly you have no choise in the long run. VB6 is replaced by VB.NET, so
MS will drop the support for it entirely in a few years.
>
>
>
On Feb 16, 5:01 am, "Earl" <briks...@newsg roups.nospamwro te:
I miss VB6 and "classic" ADO ... but I aint going back. There are too many
new tools that make my life easier. I'm sure that was part of the Microsoft
master plan. However, if you like VB.Net, you would probably like C# even
more. The hands, wrists, and bursitis appreciate not having to type asmuch.
new tools that make my life easier. I'm sure that was part of the Microsoft
master plan. However, if you like VB.Net, you would probably like C# even
more. The hands, wrists, and bursitis appreciate not having to type asmuch.
"Master Programmer" <master_program ...@outgun.comw rote in message
>news:uWxC0sUUH HA.868@TK2MSFTN GP05.phx.gbl...
>I love VB.Net! The next version is going to be even better. I'm sorryif I
>offended anyone with my rants. Please forgive me. OK?
>offended anyone with my rants. Please forgive me. OK?
--
Göran Andersson
_____http://www.guffa.com
Comment