Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!uunet.UU.NET!sef
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.std.unix
Subject: Re: access permissions in 1003.1
Message-ID: <1991Jun21.000502.8185@uunet.uu.net>
Date: 19 Jun 91 20:05:26 GMT
References: <1991Jun5.201559.11784@uunet.uu.net> <1991Jun12.043706.18456@uunet.uu.net> <1991Jun12.235808.20822@uunet.uu.net> <1991Jun15.175831.6319@uunet.uu.net>
Sender: usenet@uunet.uu.net (UseNet News)
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 19
Approved: sef@uunet.uu.net (Moderator, Sean Eric Fagan - comp.std.unix)
Originator: sef@uunet.UU.NET
Nntp-Posting-Host: uunet.uu.net
X-Submissions: std-unix@uunet.uu.net

Submitted-by: peter@ficc.ferranti.com (Peter da Silva)

In article <1991Jun15.175831.6319@uunet.uu.net> sef@kithrup.COM (Sean Eric Fagan) writes:
> have all "illegal" symbols be "safe" (__select, for example).  All library
> routines are written to use the __ names; then, you have the linker accept
> an option that tells it to try to ignore the leading __ if there are
> unresolved externals.

You could implement this simply by having the library contain duplicate
symbol table entries for __x and x, with the same offset. You could
handle it in a separate pass after compilation before creating the
library. No extra work should be needed in the librarian, compiler, or
linker!
-- 
Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180;
Sugar Land, TX  77487-5012;         `-_-' "Have you hugged your wolf, today?"


Volume-Number: Volume 24, Number 16