X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Fri, 24 Jul 2015 13:45:47 -0400
Message-Id: <201507241745.t6OHjljI001879@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to:
	<CAOP4iL2pCYKZZVdqdSEqJKPz0cAA6fb0+3Ws5MbM+UxJXAxaOQ AT mail DOT gmail DOT com>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] PCB development introduction 0.1
References: <55B001A8 DOT 5010501 AT iae DOT nl> <CAOP4iL2pCYKZZVdqdSEqJKPz0cAA6fb0+3Ws5MbM+UxJXAxaOQ AT mail DOT gmail DOT com>
Reply-To: geda-user AT delorie DOT com


> I'm suprised that no one has come up with a tool that does this
> automaticly.  Simply print a list of all variables,constants and
> functions.  Show where they are definded and where they are used.

A cross reference doesn't help you understand the code, or know why
it's designed the way it is.  Myken's doc is a sorely needed good
start on helping new developers come up to speed on pcb by explaining
the organization of the code (at the file and flow level) and how/why
it got that way.

If you *do* want a cross-reference, just use etags.