There are units that come with Delphi 3 and C++ Builder 4 that were not a
part of any system packages. Because of this, IBO was trying to include
those system units in its packages. My solution was to just go ahead and
make a package for those units to keep them out of my hair. Thus, it was
just finishing up what Borland should have done. Anyone else using those
units would then just tie into the packages instead of hitting the units
directly.

Hope this helps clear things up.

Jason

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Salvatore Besso
> Sent: Thursday, July 20, 2006 10:30 AM
> To: Lista IB Objects
> Subject: [IBO] Puzzle
>
>
> hello all,
>
> there is a thing that has always puzzled me :-) Up to version
> 4.6A, the IBO
> package contained one isolated Vcljpg30.dpk package (was it
> for Delphi 3 or
> for some C++ version?). With the latest version 4.6Bc there
> are two isolated
> packages, Vcljpg30.dpk and Vcljpg35.dpk. What are they
> supposed to serve
> for? Are they orphan packages that have to be removed from
> future versions?
>
> Regards
> Salvatore