Stephen Posey wrote: > 1. You don't need to actually include PersonalUnit.pas in the package Unit > list, as long as it's visible on the Package Project's search path it will > still be available.
If any unit in the package uses PersonalUnit, then PersonalUnit must be accounted for in the package. It must either be contained by the package directly, or it must be contained in some other package that the first one requires. Merely being on the search path isn't sufficient; the package needs to know where it's going to find that unit at run time, and DCUs aren't used at run time. If a unit isn't accounted for in one of the two mentioned ways, then the compiler will implicitly include the unit in the package when the package gets compiled. The compiler issues a warning when this happens, and it's a warning that must never be ignored. As an isolated incident, it's not too bad to have a unit included implicitly, but if the same unit gets implicitly included into more than one package, then those two packages cannot be loaded simultaneously in the same program. When the compiler warns that a unit has been included implicitly, either add the unit explicitly, or find the package the unit is already in and add it to your package's "requires" list, and then recompile your package. -- Rob _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
