home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.next.software:1513 comp.lang.objective-c:527
- Newsgroups: comp.sys.next.software,comp.lang.objective-c
- Path: sparky!uunet!caen!zaphod.mps.ohio-state.edu!menudo.uh.edu!yzhao
- From: yzhao@cs.uh.edu (Yi Zhao)
- Subject: etags, ctags, ...
- Message-ID: <1992Sep10.211727.5175@menudo.uh.edu>
- Sender: usenet@menudo.uh.edu (USENET News System)
- Nntp-Posting-Host: rodin.cs.uh.edu
- Organization: Computer Science dept., Univ. of Houston (Main Campus)
- Date: Thu, 10 Sep 1992 21:17:27 GMT
- Lines: 22
-
-
- I have some problems in using [e/c]tags with Objective-C files on NeXT
- computers. etags does not recognize Objective-C constructs. ctags recognize
- some Objective-C constructs, in a typical NeXT way: you never know why.
- Some of the problems I had are:
-
- . If you use @class for some class A, it only finds the place to
- where @class A is declared, not the place where @interface A is
- defined.
- . For methods, sometime it finds the method in the .h file, while
- sometimes, it finds the method in the .m file.
- . You cannot find an alternate definition of the tag in Edit.app by
- Source command.
-
- Generally, I prefer to use etags with Emacs. But unfortunately, my version
- of etags does not support Objective-C constructs. So the question is: is there
- a version of etags knowing Objective-C constructs in the net? or any other
- advices regarding ctags on NeXT?
-
- Any advice is appreciated.
-
-
-