Re: VB6, VB2005, or Something Else?

Paul,

¤ 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. ;-)"

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.

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.

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.

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.

Gary


.