BorlandTalk.com

Atmapuri · Guest

Hi!

1.) Delphi packages have to be compiled with linker options set for
C++ and you dont need to create separate C++ packages to
use Delphi components. Saves a lot of disk space also, because
the same binaries are shared between C++ and Delphi.

2.) In BCB6 there was no way to set global Include path.
BDS2006 has one Search path setting for Lib and Include paths.

3.) In BCB6 I had to manually add lib files from the search path to
the project, for the project to find them. BDS2006
finds them on its own.

The Delphi/C++ package interaction has been cleaned up
increadibly. Why didnt this happen 5 years ago?

Now its actually possible to install a set of Delphi components,
run the C++ demo application and it simply works :)

Other observations:
- Project converted from BCB6 gave cryptic errors
and I had to recreate it.
- one hpp import declaration changed and I had to
fix that. (it seems to have changed for the better).
- for some reason, my app compiles and run but
gives me a series of AV's for reasons yet unknown, when
I try to use some of its features... (need to debug that).

General Impression:
Very impressive, but not completely smooth.

Best Regards!
Atmapuri

bryan patrick · Guest

Please tell me this is fixed... (Or I've been doing it wrong all these
years).

I import a commercial VCL component in BCB6 (like TMS's VCL controls).

When I drop a component on a BCB form, BCB pops open a dialog to find the
..h file. Every time I have to go find the .hpp file manually. Then BCB
puts the correct #include "whatever.hpp" in the source.

This bugs the bejesus outta me.

Bryan.

"Atmapuri" <janez.makovsek (AT) usa (DOT) net> wrote