🚀 go-pugleaf

>For example, if a function contains this:

>#ifdef vax
>     foo ();
>#endif

>and you happen to be on a sun, by the time cc1 is running there is no
>trace of the fact that a call to foo was present there.

>If you rely on incomplete data for doing maintenance, bugs will
>result.  When you change the way to call foo, you need to find *all*
>the calls, not just those that happen to be enabled on the target you
>are using today.

	I belive the only downside of this is that you have to build
        the call tree once for each target you are supporting. Its a
	productivity hit but, in my mind this is a hit worth taking.

>For this reason, I believe cross-referencing ought to be done by
>parsing the source directly, *without* going through cpp.

	But why should one have to re-do somthing that the compiler is
	doing anyway ... I might get it wrong.

  I also agree with jmg@inference.com (Jeff Greif) that macro expansion
is important too!

-will d.