Re: VB6, VB2005, or Something Else?

Paul,

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

Precisly, Microsoft is the source of my pain.

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

We were talking about GoSub, but porting the code requires a lot more than
fixing Gosubs.

Someone here, I thought it was you, was just saying that While...Wend
could be easily replaced using
Do...Loop.

True.

So what added benefit is provided in doing so?

I don't understand your question.

Wouldn't that be required in order to declare it as superior?

Do...Loop is superior to While...Wend. What's the point?

¤ > ¤ 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.

Your arguments remind me of one of the Dilbert cartoons. It has Dogbert
answering a client about a problem with the software. Dogbert convinces the
client that the problem is in his head and that he needs to have his head
scanned. Dogbert then convinces the client to stick his head in the
microwave.

I would sure hate to be one of your clients...

As to Microsoft, I think where they went wrong was to consider VB6
programmers like novice users. The problem is that we are programmers. Some
of us have been programming longer than many on the .Net team. We have a
very good idea of what can and can't be done. We know when we have been
shafted. The problem is that now we are stuck between a rock and a hard
place. We will be complaining for a long time to come.


Gary


.

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: VB6, VB2005, or Something Else?
    ... Microsoft is the source of my pain. ... We were talking about GoSub, but porting the code requires a lot more than ... ¤> ¤ future. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤>> The Do...Loop that tests the condition at the top is no more capable ... ¤>> alternate between the two without a change in functionality. ... GoSub isn't even remotely comparable ... also remember there was a fair amount of outcry when Microsoft simply changed Wend to End ...
    (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)
  • 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)
Loading