Hi Eric,
a bug in semantic-el.el:
Function: `semantic-documentation-for-tag' uses `documentation-property' with only
one arg but this function requires in both XEmacs and GNU Emacs at least two args
and one optional third arg!
A question to this function `semantic-documentation-for-tag':
At the end it calls `semantic-emacs-lisp-obsoleted-doc' and produces therefore
a result like the following when called for semantic-documentation-for-tag:
"Return the documentation string for TAG.
Optional argument NOSNARF is ignored.
When i call C-h f for semantic-documentation-for-tag then i get:
semantic-documentation-for-tag is a compiled Lisp function in `semantic-doc'.
(semantic-documentation-for-tag &optional TAG NOSNARF)
This function can be overloaded (see `define-mode-local-override' for details).
It makes the overload `semantic-find-documentation' obsolete.
Find documentation from TAG and return it as a clean string.
TAG might have DOCUMENTATION set in it already.  If not, there may be
some documentation in a comment preceding TAG's definition which we
can look for.  When appropriate, this can be overridden by a language specific
Optional argument NOSNARF means to only return the lexical analyzer token for it.
If nosnarf if 'lex, then only return the lex token.
You see the difference. My question is about this @obsolete{...}. Is this a convention
and the emacs-docu-mechanism converts this to that i see when i call C-h f?
Suppose i want to write a tool which gives my the docstring for a certain semantic-tag.
Should i then use `semantic-documentation-for-tag' but i do not want to display
this @obsolete{}-stuff...is there already a way to convert this to a human readable
display (e.g. as done by C-h f)??
Thanks for help,
Klaus Berndl                     mailto: klaus.berndl@sdm.de
sd&m AG                         http://www.sdm.de
software design & management
Carl-Wery-Str. 42, 81739 Muenchen, Germany
Tel +49 89 63812-392, Fax -220