From: utzoo!decvax!cca!gwyn@Brl@sri-unix Newsgroups: net.unix-wizards Title: Re: Naming Conventions for System Libraries Article-I.D.: sri-unix.3384 Posted: Tue Sep 21 01:07:26 1982 Received: Tue Sep 21 08:30:13 1982 From: Doug GwynDate: 17 Sep 82 5:04:45-EDT (Fri) The usual solution to your problem is to declare your own routines "static". That way they're not known to the linker. Of course this doesn't solve the problem of entry points in a multi-file program conflicting with library names. In this case the only recourse is to check each of your externally- accessible interface routines (there shouldn't be too many) against the appropriate library namelists. Sometimes it is actually useful to be able to replace a system library routine by one's own version, so there are positive aspects to the design too. A complete solution to the problem requires substantial support from the linker. Try talking IBM or DEC into this and see what happens!