Re: Turbo Basic Explorer
- From: "Clinton R. Johnson" <spam@xxxxxxxxxxxxx>
- Date: 15 Sep 2006 08:36:00 -0700
mamcx wrote:
Like for example having more than 5000 warning and error for convert
a vb.net (asp.net) project from 1.1 to 2.0,including 1500+ for a non
visual, no asp.net, code only library?
Without seeing the project and the settings exactly, I would be ill
informed to suggest a reason for the warnings and errors. After all, I
could suggest anything from a marginal port, failure to correctly
configure the VS2005 IDE correctly for the lesser restrictions,
incompent programmers to things I probably can't even guess, perhaps
even dependandies on 1.0 assemblies that are not available in 2.0 as
yet.
Warnings themselves do not quality as a "Break" in the language.
Delphi does love to bitch endlessly itself until you turn off a number
of compiler flags (honest, this is NOT nor ever will be a dotnet
project, I don't care if typecasting and pointers are dotnet no-nos)
So, like I say, without seeing the code itself, I would not be
automatically inclined to blame MS. Heck, I've a had a few Delphi
components that suddenly stopped compiling with a version change
because I conflicted with new methods in parent VCL & RTL objects. Is
that Borland deliberately out to get me?
.
- Follow-Ups:
- Re: Turbo Basic Explorer
- From: mamcx
- Re: Turbo Basic Explorer
- References:
- Turbo Basic Explorer
- From: TDaniel
- Re: Turbo Basic Explorer
- From: Craig Stuntz [TeamB]
- Re: Turbo Basic Explorer
- From: Clinton R. Johnson
- Re: Turbo Basic Explorer
- From: mamcx
- Turbo Basic Explorer
- Prev by Date: Re: Turbo Basic Explorer
- Next by Date: Re: Compiling Unit?
- Previous by thread: Re: Turbo Basic Explorer
- Next by thread: Re: Turbo Basic Explorer
- Index(es):
Relevant Pages
|
|