>>> "Jans, Hauke" <email@example.com> seems to
>The advantage is that you can use the type QF in prototypes
>and let the compiler check the type validity for actual parameters.
>So you could write the following prototypes:
>and if you call i.e. setQF(QF_OK) that compiles ok,
>but if you use setQF(0) you get a compiler warning / error.
>This is common practice and i think it should work within semantic also.
[ ... ]
The original definition of QF is parsed, but it is put as a member of
QF. If you put the cursor in that definition, and type:
M-x semantic-test-all-format-tag-functions RET
you will see in the last entry (the raw tag) that all the entities are
there. The design issue is that the definition is hidden from the
tools by this C idiosyncrasy. Recently the idea of an alias was
added, but I haven't had time to apply it to C typedefs. This that
case, there would be something documented that tools could look for in
order to display things properly.
If I recall, you will find that smart completion on those entities
should work ok.
Eric Ludlam: firstname.lastname@example.org, email@example.com
Home: http://www.ludlam.net Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org