[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 44.392::delphi_in_dec

Title:Borland Delphi conference
Moderator:BROUGH::DAVIES
Created:Tue Mar 12 1996
Last Modified:Fri May 30 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:33
Total number of notes:110

26.0. "Delphi & C++ Builder..." by BROUGH::DAVIES (Hype is a 4 letter word !) Mon Mar 17 1997 15:47

Now that Borland have released C++ Builder all of us Delphi Pascal 
programmers can write C++ code ! Do we want to you ask. I'm not so
sure I do but I have done some testing using some Delphi components I have
written. They work perfectly from C++ !.

Personally I think I will stick with Delphi. How there is no reason not to
use both Delphi & C++ in a project.

At the Recent Windows-97 show Borland was demoing a beta version of
Delphi97. Very nice. Los of advances in the GUI like, intuitive typing of
variable names. 

On a down side, I moved the PAradox application I developed a couple of 
years back onto a P133 with 40Mb of RAM. It really flies. There is probably
no performance incentive to migrate the app (30+ forms) into Delphi. The user
is very happy indeed.

Stephen Davies

T.RTitleUserPersonal
Name
DateLines
26.1MARVIN::GOODWINPete GoodwinFri May 02 1997 11:1026
    I bought the standard version of C++Builder (I'm more interested in
    Delphi) and found it a little shaky as a product.

    The help files are rather massively broken. Lots of broken links etc.
    Worse than the Delphi 2.0 product!

    I found a couple of oddities with the product itself. My usual test for
    a C/C++ compiler is to throw it some big packages:

    * POVray, a public raytracer written in C
    * PNG library
    * JPEG library

    With POVray, I couldn't build it with the IDE, I had to use command
    line tools and avoid the VCL. It seems if you put the following lines
    anywhere, you can get mysterious undefined macros etc.:

    #include <vcl/vcl.h>
    #pragma hdrstop

    It looks as though the precompiled headers might be broken.
    
    With both the PNG and JPEG libraries I got a wonderfully descriptive
    'unknown error #1' which randomly came and went.
    
    Pete.