Path: utzoo!mnetor!uunet!mcvax!ukc!its63b!aiva!richard
From: richard@aiva.ed.ac.uk (Richard Tobin)
Newsgroups: comp.lang.c
Subject: Re: Machine specific predefined names
Message-ID: <265@aiva.ed.ac.uk>
Date: 25 Feb 88 23:00:50 GMT
References: <1988Feb17.115402.12739@light.uucp> <1988Feb21.015424.20436@utzoo.uucp>
Reply-To: richard@uk.ac.ed.aiva (Richard Tobin)
Organization: Bannerman's Bar, Cowgate, Edinburgh
Lines: 19

In article <1988Feb21.015424.20436@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>while something like "open" clearly ought to be available under that
>name, it would also be nice to have it available under some implementor-
>reserved name like "__open" so that, say, "fopen" could call it without
>requiring the user to avoid using "open" as the name of one of his own
>functions.  This would greatly reduce the headache of having to remember

It would also be nice if a user could easily replace the open() function
(for example) with one of their own that could call the original one.  But
in such a case the user might well want fopen() to call the new one, so
having __open available wouldn't help.  The desired effect can sometimes
be achieved by tricks when linking, but there doesn't seem to be a clean
way to do it.

-- Richard
-- 
Richard Tobin,                         JANET: R.Tobin@uk.ac.ed             
AI Applications Institute,             ARPA:  R.Tobin%uk.ac.ed@nss.cs.ucl.ac.uk
Edinburgh University.                  UUCP:  ...!ukc!ed.ac.uk!R.Tobin