Re: VB6, VB2005, or Something Else?

On Mon, 3 Apr 2006 20:22:38 +0100, "Gary Nelson" <gn@xxxxxxxxxx> wrote:

Gary,

¤ > ¤ I see you have very little interest in ecology.
¤ > ¤
¤ >
¤ > No I don't. But then there isn't really any relationship between ecology
¤ > and GoSub.
¤
¤ It was just an illustration on your attitude. You are only interested in
¤ those things that you can see are of immediate benifit to you personally.
¤

Not sure where you came up with that conclusion. There are plenty of folks who feel the same way as
I do, just as I'm sure there are those who feel the same way as you do.

Am I calling you stubborn and selfish for denying that there are alternative solutions? Isn't one of
the responsibilities of a programmer to develop alternative solutions when a change to the platform
or language occurs?

¤ > ¤ > You just said GoSub wasn't the same and I would agree. This isn't an
¤ > issue
¤ > ¤ > of redundancy. It's a
¤ > ¤ > question of disposing of a dated construct that has a suitable
¤ > ¤ > replacement.
¤ > ¤
¤ > ¤ Wouldn't it be a good idea to get rid of For...Next also, since it has a
¤ > ¤ suitable replacement?
¤ > ¤
¤ >
¤ > For...Next isn't considered dated. Why would it be considered unsuitable.
¤ > Nothing really changed in
¤ > the language to make it such.
¤ >
¤ > It's also quite frequently used and was enhanced to support objects.
¤ > Nobody ever stated that a
¤ > language component should be removed solely because there are
¤ > alternatives.
¤
¤ It's all a matter of point of view. If it became the *in* thing to consider
¤ it outdated, I can see Paul removing all the for...nexts from his code. By
¤ the way, why was While...Wend (End While) left in? It is defintely dated.
¤

Once again, there has never been any functionality added to the language which actually improved
upon the intended purpose of this construct, rendering it dated. It's frequently used and nothing
has changed that. The same is not true for GoSub.

¤ > No I just choose not to dwell on it because it does little or no good.
¤ >
¤ > You can only carry the torch for so long until the flame goes out.
¤
¤ Unfortunately the flame is not going to go out for a long time yet. In our
¤ company we continue to churn out hundreds of lines of VB6 code a day, and I
¤ am sure that there are thousands of companies out there doing the same. Not
¤ to speak of all the VBA code being created daily. We are not happy and we
¤ will continue to complain as long as it hurts.

Sounds like it will be hurting for a long time until you decide to address it. In addition, if you
are continuing to use GoSub in new code then you have little to complain about.


Paul
~~~~
Microsoft MVP (Visual Basic)
.

Relevant Pages

  • Re: Microsoft Printer Compatibility Library 1.0 now available
    ... That it is, and you're right, RPG III was the first version that had real ... upgrade and it's not going to happen all that often. ... works, and that's a GREAT thing, but it's too bad the totally hosed language ... ¤ ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... I happen to think core language is more important because there is ... ¤> ¤ Andre, ... to the extensions would ...
    (microsoft.public.vb.general.discussion)
  • Re: VB coverage in new online mag - VB6 or VB.NET?
    ... >> ¤ successfully, others did not. ... >> to that environment. ... Don't confuse the product with the language. ... > realize, of course, that dotNet is not TheLastBigThing any more than Win32 ...
    (microsoft.public.vb.general.discussion)
  • Re: Developer Use of Visual Basic Plummets
    ... There is no way to know whether Microsoft will change the product ... ¤ ... Why is it confusing? ... but syntax is a very small part of a language. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... widely used programming ... language during that time. ... there sure as heck a lot more VB programmers than COBOL ones. ... ¤> Visual Basic would have continued to be the also-ran. ...
    (microsoft.public.vb.general.discussion)