Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site elsie.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!rlgvax!cvl!elsie!mark
From: mark@elsie.UUCP
Newsgroups: net.unix,net.lang.c,net.unix-wizards
Subject: Re: Qualified Names mean you don't break the C Library
Message-ID: <1128@elsie.UUCP>
Date: Wed, 25-Jul-84 17:30:40 EDT
Article-I.D.: elsie.1128
Posted: Wed Jul 25 17:30:40 1984
Date-Received: Sat, 28-Jul-84 00:44:46 EDT
References: <8430@watmath.UUCP>
Organization: NIH-LEC, Bethesda, MD
Lines: 19

<>
One way to avoid collision between your own subroutine names and those that
may be used by the C libraries is to declare all routines that are used only
in a single source file to be static. Thus if I want to write my own malloc,
I write:
	static malloc(size)
	unsigned	size;
	{
	...
	}
This will (should) not interfere with any malloc's used by the library. Of
course if I want to this malloc from other files of a multi-file source, I
can't use static so I'd better change the name.

-- 
Mark J. Miller
NIH/NCI/DCE/LEC
UUCP:	decvax!harpo!seismo!umcp-cs!elsie!mark
Phone:	(301) 496-5688