Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!orchid!jagardner
From: jagardner@orchid.UUCP
Newsgroups: comp.lang.c
Subject: Re: ANS C Macro Processing
Message-ID: <11446@orchid.waterloo.edu>
Date: Thu, 29-Oct-87 18:25:14 EST
Article-I.D.: orchid.11446
Posted: Thu Oct 29 18:25:14 1987
Date-Received: Sat, 31-Oct-87 11:14:13 EST
References: <167@sdti.UUCP> <11322@orchid.waterloo.edu> <1880@homxc.UUCP>
Reply-To: datanguay@watbun.waterloo.edu (David Tanguay)
Organization: U. of Waterloo, Ontario
Lines: 14

In article <1880@homxc.UUCP> lewisd@homxc.UUCP (David Lewis) writes:
>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?

I'm not sure exactly what you mean. One way to see what CPP expands a macro
to be is to run a source file with the macro in it through CPP and look at
the output. In some environments this involves either invoking C with
appropriate arguments or calling the cpp pass directly. Another way
is to carefully read the dpANS C section on CPP and pretend you're it.
The latter will place your sanity in jeopardy.

David Tanguay, Software Development Group, University of Waterloo