Re: VB6, VB2005, or Something Else?
- From: Andre Kaufmann <andre.kaufmann.bei@xxxxxxxxxxx>
- Date: Tue, 04 Apr 2006 07:59:13 +0200
Dan Barclay wrote:
"Andre Kaufmann" <andre.kaufmann.bei@xxxxxxxxxxx> wrote in message news:%23iIejytVGHA.1688@xxxxxxxxxxxxxxxxxxxxxxxGary Nelson wrote:Paul,I once thought the same way, that Microsoft could have done better, let's say like Borland did with Delphi. But after reading the following article www.itwriting.com/frozenvb6.php I'm not sure about that anymore.
[...]
Someone here seems to have missed the point.
Should add: I'm not a VB expert to be able to 100% verify the statements made in this article.
I didn't waste my time reading every word of the article. It was clear within a minute that the author was interested in selling a point of view rather than facts.
We had a discussion about the VB6 about a year ago and you made it clear that the VB.NET changes have broken business/math code.
You referred (as an example) to the integer size changed, I have checked it and the upgrade tool does upgrade the code correctly.
Don't get me wrong, I agree that too much has changed and not all changes have been necessary. I also agree that the integer size changes breaks code compatibility. Meaning you can't go back to VB6 or using just the same code.
I'm just referring to the point that also core code (formulas) has been broken so that you can't >upgrade<, which the article states that's not the case.
I'm not that an VB6 expert to verify this statement, but would be glad if you could give one.
The changes made in the VB language were by specific decision to "clean up" the language rather than any requirement of the platform change. The one exception to that was the loss of Deterministic Finalization.
OO and structure changes could easily have been added without breaking existing language features.
They could have been added. But the current VB6 "object" model conflicts with the "new" object model. They could have been implemented both, no doubt, but that would have lead IMHO to a language monster.
I'm not making that up. That comes from MS.
May be, that the article has been paid or influenced by Microsoft. Though the site seems to have articles from Borland too. I hadn't a look at them, but will do so.
I understand that you've got burned by the VB.NET changes, but what I don't understand is that you are moving completely to Delphi. Don't get me wrong. I 'm using Delphi too and regarding language stability it's a very good alternative. But yet you are restricted to a single vendor. Why don't you move your internally business code to C++ ? That shouldn't be a discussion about the vendor Borland or Microsoft nor do I have anything against Borland (regarding Delphi).
Borland has a C++ compiler too and also other operating systems.
Wouldn't that be the natural move of a burned VB6 developer to move to C++ with the business code and use e.g. Delphi for the rest of it ?
Dan
Andre
.
- Follow-Ups:
- Re: VB6, VB2005, or Something Else?
- From: Dan Barclay
- Re: VB6, VB2005, or Something Else?
- From: Bob Butler
- Re: VB6, VB2005, or Something Else?
- References:
- Re: VB6, VB2005, or Something Else?
- From: Gary Nelson
- Re: VB6, VB2005, or Something Else?
- From: Andre Kaufmann
- Re: VB6, VB2005, or Something Else?
- From: Dan Barclay
- Re: VB6, VB2005, or Something Else?
- Prev by Date: Re: VB6, VB2005, or Something Else?
- Next by Date: Re: See if file exists
- Previous by thread: Re: VB6, VB2005, or Something Else?
- Next by thread: Re: VB6, VB2005, or Something Else?
- Index(es):
Relevant Pages
|