Re: VB6, VB2005, or Something Else?

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Fri, 7 Apr 2006 10:07:30 +0100, "Gary Nelson" <gn@xxxxxxxxxx> wrote:

Gary,

¤ > ¤ 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.
¤
¤ Could it be "I'm not the one engaged in the crying game. ;-)"
¤

Then given what we have known for several years now, how would you describe it?

¤ > 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?
¤
¤ I'm not denying that there are alternative solutions. The problem with the
¤ alternative solutions is that they would bankrupt our company. That is NOT a
¤ solution.
¤

So if making the change from GoSub to Subs/Functions would bankrupt your company then it sounds like
you should just leave the code as it is.

¤ > Isn't one of
¤ > the responsibilities of a programmer to develop alternative solutions when
¤ > a change to the platform
¤ > or language occurs?
¤
¤ My job is to develop solutions to my clients' problems. It would have been
¤ nice if that was MS's job too.
¤

They do but apparently that *is* the problem for some.

¤ > 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.
¤
¤ Do...Loop doesn't improve on While...Wend (End While)? Even if it is
¤ frequently used, it would be very simple to do a replace.
¤

Probably so, but why?

I'm not sure why you're focusing on one factor, as other's have, when I've mentioned at least two or
three.

¤ > 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.
¤
¤ If addressing it means bankrupting my company, yes it will be a very long
¤ time. My guess is that it will be the same for others in the same boat.

I'm sorry but I can't believe that the basis for the survival of your company is dependent upon
GoSub.


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

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... ¤ alternative solutions is that they would bankrupt our company. ... ¤> or language occurs? ... The same is not true for GoSub. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 Error Handling
    ... ¤> I guess we'll never know since you didn't make an attempt to explain ... Besides, alternative solutions don't usually ... Microsoft MVP ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> ¤ I see you have very little interest in ecology. ... But then there isn't really any relationship between ecology ... Am I calling you stubborn and selfish for denying that there are alternative solutions? ... ¤> the language to make it such. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 Error Handling
    ... ¤> ¤ There is a valid reason for this, but I'm doubtin' you'd understand it. ... alternative solutions don't usually involve Java although I've ... Microsoft MVP ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> language and it can be easily ... But if you're using several GoSubs in a Sub or Function then it's ... The ability to write bad code is not an excuse to use GoSub. ... I'd have to use a knife, but I would miss the screwdriver. ...
    (microsoft.public.vb.general.discussion)