I use \p to mark mentions of formal parameters. The manual suggests that
this is indeed \p's intented role ("You can use this command to refer to
member function parameters in the running text"). Unfortunately that same
manual also supplies an excessively specific operational description of
\p's effect ("Displays the parameter <word> using a typewriter font. ... To
have multiple words in typewriter font use <tt>multiple words</tt>").
Worse, based on this operational description it asserts equivalence
between \p and \c ("Equivalent to \c").
My generated documentation uses sans serif fonts for both proportional and
fixed width. Changing to typewriter is too subtle to clearly call out a
token as a formal parameter name. I would like to see \p more strongly
tied to marking formal parameters. In particular I suggest rendering
marked up parameter names using the same font, bolding and color as when
they appears in a function signature.
/john
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
