SCO externs ... too many?
Norman Kohn
nvk at ddsw1.MCS.COM
Sun Apr 23 08:30:24 AEST 1989
In article <631 at jc3b21.UUCP> davis at jc3b21.UUCP (William J Davis) writes:
>
> I am current developing a LARGE application using SCO Xenix 2.3.0...
>the loader seems unable to resolve large numbers of external references...
I encountered a similar problem under microport: there obviously is
some sort of limit to symbol table size.
I addressed this by putting related externs into structs defined
in appropriate header files: e.g.,
struct {int a,b;
char c,d,e;
} SAMPLE;
Presumably SAMPLE.a is coded as an offset off SAMPLE, and everything
in the struct gets linked up using only a single extern entry
in the linker symbol table. Moreover, this simplifies tracking
large groups of externs. For ease of management, I favor putting
related programs (related by use of specific header files)
in their own libraries when possible...
--
Norman Kohn | ...ddsw1!nvk!norman
Chicago, Il. | days/ans svc: (312) 650-6840
| eves: (312) 373-0564
More information about the Comp.unix.xenix
mailing list