Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!labrea!decwrl!hplabs!hp-pcd!uoregon!omepd!mipos3!cpocd2!howard
From: howard@cpocd2.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Possible LSC improvements
Message-ID: <971@cpocd2.UUCP>
Date: Mon, 16-Nov-87 15:25:26 EST
Article-I.D.: cpocd2.971
Posted: Mon Nov 16 15:25:26 1987
Date-Received: Thu, 19-Nov-87 04:42:43 EST
References: <6523@prls.UUCP> <9370001@hpfclp.HP.COM> <750@orstcs.CS.ORST.EDU> <328@moncsbruce.oz> <3112@husc6.UUCP>
Reply-To: howard@cpocd2.UUCP (Howard A. Landman)
Organization: Intel Corp. ASIC Systems Organization, Chandler AZ
Lines: 18

In article <328@moncsbruce.oz> conybear@moncsbruce.oz (Roland Conybeare) writes:
>I would like something more sophisticated that looks up the definition
>of the selected function name or global variable, a la vi's tag command.

In article <3112@husc6.UUCP> singer@endor.UUCP (Richard Siegel) writes:
>	Try option-double-click on a symbol. If it's declared somewhere,
>the file will be opened and the symbol declaration will be displayed.
>(This doesn't work for macros, of course...)

Why "of course"?  UNIX ctags works for both procedure names *and* macros,
so it's clearly possible to handle macros correctly.  Perhaps you just haven't
thought about it enough yet.

-- 
	Howard A. Landman
	{oliveb,hplabs}!intelca!mipos3!cpocd2!howard
	howard%cpocd2.intel.com@RELAY.CS.NET
	"Never had anything but a mother." - Mississippi John Hurt