Path: utzoo!mnetor!uunet!mcvax!tuvie!rcvie
From: rcvie@tuvie (ELIN Forsch.z.)
Newsgroups: comp.lang.c
Subject: Re: Machine specific predefined names
Message-ID: <598@tuvie>
Date: 30 Mar 88 20:04:28 GMT
References: <1988Feb17.115402.12739@light.uucp> <17033@watmath.waterloo.edu> <242@sdrc.UUCP> <378@wsccs.UUCP> <3225@haddock.ISC.COM>
Reply-To: rcvie@tuvie.UUCP (Alcatel-ELIN Forsch.z.)
Organization: Technical University of Vienna
Lines: 16

In article <3225@haddock.ISC.COM> karl@haddock.ima.isc.com (Karl Heuer) writes:
>Moreover, not all systems implement putchar() as a macro.  If you
>try to redefine *any* standard routine -- whether macro or function -- the
>result should be, and is, undefined.  Why should the user be forced to learn
>the implementation details?

Just try the portable way and noone has to learn anything but that there
*are* some routines implemented as functions and some as macros:

#ifdef putchar
#undef putchar

<your putchar-macro/function>

		Dietmar Weickert,
			ALCATEL-ELIN Research Center, Vienna, Austria.