Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ucbcad!ames!hao!oddjob!mimsy!cvl!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: ANS C Macro Processing
Message-ID: <6605@brl-smoke.ARPA>
Date: Thu, 29-Oct-87 23:22:35 EST
Article-I.D.: brl-smok.6605
Posted: Thu Oct 29 23:22:35 1987
Date-Received: Wed, 4-Nov-87 05:32:23 EST
References: <167@sdti.UUCP> <11322@orchid.waterloo.edu> <1880@homxc.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
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?

Why ask the list; you do have a manual, don't you?
See if it says that your "cc" command supports a -P or -E option.

If you have a separate text-to-text preprocessor, it is probably
called /lib/cpp and you can also run it by itself and type stuff
at it to see what it does.

This is all implementation-dependent; not all C compilers have an
explicit preprocessing phase.  Sometimes it's bundled into the
lexical analyzer.