Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!phigate!prle!prles2!cstw68!meulenbr
From: meulenbr@cstw68.prl.philips.nl (Frans Meulenbroeks)
Newsgroups: comp.os.minix
Subject: Re: Zen and the Art of Library Programming
Message-ID: <830@prles2.UUCP>
Date: 2 Jan 90 12:24:28 GMT
References: <22630@princeton.Princeton.EDU>
Sender: nobody@prles2.UUCP
Reply-To: meulenbr@cst.prl.philips.nl (Frans Meulenbroeks)
Organization: Centre for Software Technology, Philips Eindhoven
Lines: 16

In article <22630@princeton.Princeton.EDU> nfs@notecnirp.UUCP (Norbert Schlenker) writes:
>Every (!) library function becomes a simple front-end for another function
>which does the work.  Every library function can call ONLY the underlying
>functions (I like to call them underware :-)  To avoid ANSI namespace
>conflicts, I suggest the underware's names be prefixed with two underscores.

I like the idea & hate the performance loss.
One potential problem exists: 
implementations may restrict the significance of an identifier to 6
characters, and may ignore case distinctions. (ansi draft sec. 3.1)
I don't know if this applies to minix, but if so, name clashes might
occur by prepending the names with __
(eg fputc and fputs could become __fput).
Frans Meulenbroeks        (meulenbr@cst.prl.philips.nl)
	Centre for Software Technology
	( or try: ...!mcvax!phigate!prle!cst!meulenbr)