Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!homxb!homxc!lewisd
From: lewisd@homxc.UUCP (David Lewis)
Newsgroups: comp.lang.c
Subject: Re: ANS C Macro Processing
Message-ID: <1880@homxc.UUCP>
Date: Mon, 26-Oct-87 15:11:17 EST
Article-I.D.: homxc.1880
Posted: Mon Oct 26 15:11:17 1987
Date-Received: Thu, 29-Oct-87 23:23:25 EST
References: <167@sdti.UUCP> <11322@orchid.waterloo.edu>
Organization: AT&T Bell Laboratories, Red Hill Site, NJ
Lines: 20
Summary: how to determine pre-processor expansion

In article <11322@orchid.waterloo.edu>, jagardner@orchid.waterloo.edu (Jim Gardner) writes:
> Wow! I was just about to post a similar article!
> 
> The example I've been toying with is:
> 
> #define f(a)  a+g
> #define g(a)  f(a)
> f(1)(2)
> 
> The expansion follows as:
> 	"f(1)(2)" -> "1+g(2)" -> "1+f(2)"

How do you determine what the pre-processor expands a macro to be?
Is there any way to take a look at the results of such an expansion?
Can you see the intermediate file produced after all #includes and 
#ifdefs and #defines are evaluated?
-- 

David B. Lewis    {ihnp4,allegra,ulysses}!homxc!lewisd
201-615-5306 EDT