Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Assorted C Questions
Message-ID: <10994@smoke.BRL.MIL>
Date: 9 Sep 89 01:18:33 GMT
References: <4294@udccvax1.acs.udel.EDU> <1989Sep6.160004.19253@utzoo.uucp> <283@crdos1.crd.ge.COM> <1989Sep7.162354.20722@utzoo.uucp> <14556@haddock.ima.isc.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <14556@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
-In article <1989Sep7.162354.20722@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
->(And the basic point remains: the [function-like macro] name is recognized
->only when there is a '(' after it.)
-It should be noted that this feature is new to ANSI C, and should not be
-exploited by programs that need to be portable to pre-ANSI environments.

It's more the acceptance of the un-() occurrence as a valid literal token
that is new.  PCC used to say "argument mismatch" when it encountered such
an instance, for eaxmple.