Re: CodeGearT Introduces DelphiR for Win32R, Providing RADDevelopment for Windows VistaR and AJAX



Captain,

I've said this before, but I'll say it again. I REALLY think CodeGear ought to make every Delphi IDE release non-breaking, by allowing projects to have a specific version of the compiler associated with the project code. So a project would be say a "Delphi 6.0 project" but hosted in the newest IDE. The IDE would come with all the old versions of the compiler, and a project option would indicate which version to use at compile time.

now, this would be really cool, indeed. however, i'd foresee that this would be trickier then it may sound - fr example opening any form in form designer would add new properties that the old VCL didn't understand, so the designers would also have to be made version-aware, somehow (and people would expect them to be, if they can load and compile their legacy projects)?

There is a lot of old code sitting out there that has never been upgraded to a newer version of Delphi because of the cost of upgrading the code and components. People working on these codebases would love to make use of newer IDE features, but can't as long as new IDE's are tied to breaking versions of the compiler.

indeed. i got lots of "touch once in a blue moon" projects that i'd love to consider bringing into BDS2006 or Delphi 2007 once its out - but its just not worth the effort ;(. that said, the biggest effort (not problem, but effort) are third party packages. my projects use a lot of stuff, including custom packages, and custom visual controls build with the CDK (anyone remember that ;), and /those/ are what really keep me from "simply" getting the projects into the newer IDE - not the compiler and core RTL itself (which i pretty much trust, backward compatibility wise).

In addition, I really think Delphi needs to be integrated more closely with C++, so that I can take a C++ file and just simply use it in a Delphi project the way I'd use a Delphi unit, with the IDE taking care of interfacing the two. It would be THE BOMB if I could take open source C++ code and just use it in my Delphi projects effortlessly. When C++Builder came out it looked suggestive of this possibility, though it did it in the other direction, thunking Delphi code for use in C++ projects. (Unfortunately, the last time I tried to just compile some open-source C++ in the C++ personality of BDS I got nowhere.)

indeed, again. i actually excitedly bought (pre-ordered) C++Builder 1 for this very reason, back when it came out - i didn't want to write C++ code, i wanted to *reuse* it in my Delphi apps. :(

In fact, to be honest, I don't think a person should need something as heavyhanded as .NET to be able to mix and match languages in a project.

heavyhanded?


--
marc hoffman
Chief Architect
RemObjects Software
http://www.remobjects.com

and the fifty-two daughters of the revolution
turn the gold to chrome
.



Relevant Pages

  • Re: Why arent you upgrading?
    ... Stable IDE - this is first and foremost before anything else. ... MS alternate choice - As I see it the reason Delphi became so ... better database support ... Then announce that 64-bit native compiler is in progress and started. ...
    (borland.public.delphi.non-technical)
  • Re: Oh man!
    ... a native code DELPHI language IDE. ... platform. ... I dont even want the IDE - just a cross compiler would be ... You could write the code using Delphi on windows and then cross compile it to any platforms supported by FPC/Lazarus. ...
    (borland.public.delphi.non-technical)
  • Re: Opportunity passed by
    ... Delphi for .NET on the ... hand has its own compiler that has to be modified to use the latest things ... has folded into .NET, ditto for a special version of the VCL, and the IDE ... C# developers, as they want/have moved to .NET 2.0, and Delphi ...
    (borland.public.delphi.non-technical)
  • Re: usual nontechnical issues
    ... I think the compiler is also nice.. ... component market reflects how well Borland did its job ... with the compiler and the IDE. ... I still think that W32 Delphi today has a component base that beats .NET's ...
    (borland.public.delphi.non-technical)
  • Alternative Future of Delphi?
    ... relevant compiler or interpreter... ... No more intricate code generation required for a particular platform ... on the Delphi compiler side. ...
    (borland.public.delphi.non-technical)

Loading