Which objects are copied to the executable file  Which objects are not copied to the dynamic libraries

Chapter 26: Packaging and Distributing an Application

Which objects are not copied to the executable file

When it creates the executable file, PocketBuilder can identify the associations you made in the painter, because those references are saved with the object's definition in the library. PocketBuilder also identifies direct references in scripts, because the compiler saves this information.

However, PocketBuilder cannot identify objects that are referenced dynamically through string variables. To do so, it would have to read through all the scripts and process all assignment statements to uncover all the referenced objects. The following examples show objects that are not copied to the executable file:





Copyright © 2004. Sybase Inc. All rights reserved. Which objects are not copied to the dynamic libraries

View this book as PDF