Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!ingr!doyle
From: doyle@ingr.com (Doyle Davidson)
Newsgroups: comp.windows.x
Subject: SYSV shared Xaw and XtInheritTranslations
Message-ID: <10118@ingr.com>
Date: 3 May 90 22:41:48 GMT
Organization: Intergraph Corp. Huntsville, Al
Lines: 38


I am attempting to make libXaw.a a shared library under 
SYSV 3.1 and I have hit a stumper.  (I already got Xlib and Xt done)
My problem is that XtInheritTranslations is defined as:

externalref int _XtInheritTranslations;
#define XtInheritTranslations  ((String) &_XtInheritTranslations)

and later used as:

BlahClassRec blahClassRec = {
    ...,
     /* tm_table         */      XtInheritTranslations,
    ...

Is the reason that is done as opposed to something like
    #define XtInheritTranslations  -1
so that the item is truly a data pointer to prevent problems
for certain architectures?  And if so, does anyone see any problem
with me changing it for my libraries and binaries?

I can't import the address of an extern data item into my shared library
and place it in initialize data (see AsciiText.c) 

Thanks in advance,

Doyle
-------------------------------
Doyle C. Davidson              
Intergraph Corp.               
Workstation Graphics Standards 
1 Madison Industrial Park      
Huntsville, AL 35806           
(205) 730-2000                 
                               
..!uunet!ingr!doyle 
    or   doyle@ingr.com
-------------------------------