Re: VB6, VB2005, or Something Else?

On Thu, 13 Apr 2006 11:26:55 +0100, "Gary Nelson" <gn@xxxxxxxxxx> wrote:

Gary,

¤
¤ > Point is that you've had several years now to decide what to do.
¤
¤ Point is, we already had too much code in place when we found out. We just
¤ want to keep our companies running.
¤
¤ > If you think that continuing to
¤ > complain about it for the next five years is going to help then I have
¤ > some bad news. That may sound
¤ > harsh and it may be unfortunate but that's the reality of it.
¤
¤ That sound like the answer from a doctor, whose opperation went wrong and
¤ left his patient with a permanent pain.

Well I guess I could understand how you would feel that way if Microsoft was the source of your
pain.

¤ > ¤ > 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.
¤ > ¤
¤ > ¤ Ignorance is bliss. As if the only problem were the GoSubs, how about
¤ > the
¤ > ¤ control arrays? How about all of the other hundreds of things that make
¤ > it
¤ > ¤ impossible to port the code?
¤ > ¤
¤ >
¤ > I'm the one who is apparently ignorant. Why ask me?
¤
¤ You're the one who said "So if making the change from GoSub to
¤ Subs/Functions would bankrupt your.."
¤
¤ I'm just clarifying that it is much worse than that.
¤

Never denied that other changes would be required. But then I thought we were talking specifically
about GoSub.

¤ > ¤ Why not? To clean up the language of course!
¤ > ¤
¤ >
¤ > How does that "clean up" the language? Is there something unusual about
¤ > the While...Wend/End While
¤ > construct? Is it somehow an implementation that is unique to the Visual
¤ > Basic language?
¤
¤ It's outdated. Do... Loop is a much superior construct.
¤

Someone here, I thought it was you, was just saying that While...Wend could be easily replaced using
Do...Loop. So what added benefit is provided in doing so? Wouldn't that be required in order to
declare it as superior?

¤ > ¤ The basis for the survival of our company is taking our code into the
¤ > ¤ future. That seems to be at the bottom of Microsoft's agenda.
¤ >
¤ > You have me convinced that it's at the bottom of yours as well.
¤
¤ There lies the problem. Microsoft & you believe that we have no interest in
¤ taking our code forward. Therefore no help is comming from those quarters.

I don't know what Microsoft thinks. What I see is every reason being offered not to consider the
alternatives and make the effort.


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

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... By the way, the preformance of Gosub in PCode was quite good, it ... ¤ ... I'm not complaining about the necessary changes, ... that Microsoft intentionally and unnecessarily made it more difficult. ...
    (microsoft.public.vb.general.discussion)
  • Re: Rolling the dice on vb6
    ... Stefan Berglund wrote: ... ¤ Yep, long gone. ... Let us say that Microsoft could write a real VB6 -> Fred ... MS could have had their business, could have had my business, and they ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... It seems to me that you are a proponent for the .net framework, ... Relating to the above 4 items: A small company selling software such as us ... Relating to the above 4 items: Can't Microsoft: ... ¤>we are. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤ Duh! ... Microsoft MVP ... GoSub is a bit dated - but no reason to kill it. ... possibly understand how a compiler or platform might work. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... want to keep our companies running. ... ¤> you should just leave the code as it is. ... Loop is a much superior construct. ... You have me convinced that it's at the bottom of yours as well. ...
    (microsoft.public.vb.general.discussion)
Loading