Re: Captain Jake's Top Ten List of what I'd like to see in thenextversion of Delphi

"Nick Hodges (Borland/DevCo)" <nickhodges@xxxxxxxxx> wrote in message
<44a56816$1@xxxxxxxxxxxxxxxxxxxxxx>
John Jacobson wrote:


The problem obviously is not technical, but economic.

That's exactly right. We could take, say, 10 manyears of compiler work
and implement this for a very, very, very, very, very small,
incremental benefit.

Do you think we should do it? ;-)

I think you ought to do something that's a little easier: put a switch in the
BDS project options that lets you choose what version of the language/RTL/VCL
the IDE and the compiler/linker should use, the same way you could choose what
version of the Java libraries/runtimes would be used in a JBuilder project.
Then in the project directories we could specify what path should apply for the
project. A D6 project would set that switch to D6-compatibility and the user
would set the project directories to D6 versions of the third-party libraries
and components used in that project. This way we could use the new IDE features
like refactoring even though we might be stuck in code that was not yet
upgraded to the latest version of Delphi. I think this would be cool.

Obviously there is a limit to how far this can go. If a user chooses D6
compatibility he obviously should not expect to be able to use components,
features, add-ins or wizards that depend on other versions of the language
(perhaps ECO falls into this category?). And it would not be worth it
economically to give users the ability to mix and match different versions
within the same project.

--
***Free Your Mind***

Posted with JSNewsreader Preview 0.9.4.2549


.