>> I would also be tempted to replace the searches that your jtags
>> script generates with line numbers. Line numbers would be
>> less tolerant of edits to files [...]
And that's exactly why they are a bad idea: As soon as you add or
delete a line, the tag jumps won't work anymore. Therefor: patterns.
>Thanks. I also found that ctags can generate tags for J scripts.
*Your* version of ctags can do that. The standard ctags version
has its supported languages and patterns hardwired, alas. That's
why I wrote jtags in first place. It will make everybody happy.
(Well, everybody using vi or ed, at least :-)
>This is what I wrote to match explicit definitions.
>/([a-zA-Z][a-zA-Z0-9_]*)[
>\t]*=:.*(noun|verb|adverb|conjuction|(1?[01234]))[ \t]+:[
>\t]*(define|0)/\1/
What's the sense in differentiating between explicit/tacit
definitions and ignoring tacit ones such as "avg =: +/ % #" ?
Martin
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
