Re: [Groff] tmac.www macro name clashes?

[Werner LEMBERG]

>
> What should I keep in mind when composing macro names for tmac.www?

The usual thing in high level languages like C is to always have a
unique prefix, say, `www-'.  I think that your choice to have `<' as a
prefix is optimal.  It is, AFAIK, unique, and it always reminds the
user that it has something to do with HTML.

> tmac.www is intended to be a stand alone macro package for Web
> sites. So it does not need ms or any other macro set to help it out.
> 
> However, if someone needs to use ms, me or other macro packages in
> conjunction with tmac.www, how do I avoid any conflicts with those
> other macro packages?

Which kind of conflicts did you encounter?  The only possibility to
avoid name clashes is to check all macro definitions in the standard
macro packages which come with groff.

Nevertheless, there is a small tool which might help you in debugging:
tmac.trace.  Say e.g.

  groff -mtrace -man -Tlatin1 2>groff.log > groff.txt

to get a trace of all macro calls/definitions in tmac.an.  You can
e.g. get an ordered list of all used macros with

  cut -d ' ' -f 5 groff.log | sort | uniq > man.log.macrolist

provided there are no warning or error messages.


    Werner