Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!uunet.UU.NET!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.std.unix
Subject: Re: access permissions in 1003.1
Message-ID: <1991Jun12.043706.18456@uunet.uu.net>
Date: 12 Jun 91 04:10:22 GMT
References: <1991Jun3.225808.8518@uunet.uu.net> <1991Jun5.201559.11784@uunet.uu.net> <1991Jun12.034858.16429@uunet.uu.net>
Sender: usenet@uunet.uu.net (UseNet News)
Organization: Kithrup Enterprises, Ltd.
Lines: 20
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: sef@kithrup.COM (Sean Eric Fagan)

In article <1991Jun12.034858.16429@uunet.uu.net> mib@geech.gnu.ai.mit.edu (Michael I Bushnell) writes:
>What about name space cleanliness at link time?  All the systems seem
>to punt on this one, and it really indicates their lack of commitment.

HP solved this, I believe (at least, according to an article in _The Journal
of C Language Translation_).  I looked into this, way back when I was
involved with development system work, and came up with a couple of
solutions, at least one of which will likely be used.  (They're both fairly
obvious.)

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.


Volume-Number: Volume 23, Number 102