From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: "ozan s. yigit" Message-ID: <4da3d9af.0203110902.159b81c3@posting.google.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit References: Subject: Re: [9fans] samuel Date: Mon, 11 Mar 2002 17:16:02 +0000 Topicbox-Message-UUID: 64a6287c-eaca-11e9-9e20-41e7f4b1d025 rsc@plan9.bell-labs.com (Russ Cox) wrote: > For many acme users, the > cscope-like tool of choice is grep, especially > since cscope doesn't compile on Plan 9 (it's too tied > to curses [sic]). i have occasionally used a small toolkit named id [later gnufied and forgotten as idutils; a non-gnu version cleaned up by mark moraes is still around in ftp.cs.utoronto.ca] it requires an identifier database be built forehand. even though it has many creaky parts, it did have a few interesting features; numeric identifiers are searched in all radixes: lid 235 0353 sys/src/cmd/dd.c sys/src/cmd/troff/hytab.c 0x00EB sys/src/cmd/tcs/tcs.c 0xEB sys/src/boot/pc/x16.h sys/src/9/boot/key.c since the database contains proper identifiers, lid regular expressions apply not to lines but to identifiers: lid '^xx' xxxincoff sys/src/cmd/troff/n3.c xxxvers sys/src/ape/cmd/make/ident.c xxyy sys/src/cmd/gs/src/gspaint.c output is path adjusted relative to the id database: lid 'xx$' errxx ../ape/cmd/expr/expr.y and so on. id tools had the idea of having scanners for different languages, but only C, assembler and text scanners were implemented. oz --- www.cs.yorku.ca/~oz | don't count your chickens in glass houses york u. computer science | until the cows come home. -- david vestal