Re: FYI: 13-gary-remove-redundant-traced-field.patch

[Akim Demaille]

| > Gary> This means that we store the flag against whichever
| > Gary> m4_token_data is stored in the named symbol when traceon is
| > Gary> invoked, and can be turned off by traceoff with the name of some
| > Gary> symbol that currently holds that m4_token_data.  I think there
| > Gary> is one small wrinkle in this approach, in that the command line
| > Gary> trace parameters will need to be stored for application a the
| > Gary> end of command line processing... 
| > 
| > Agreed.  That's the list I was referring too.  Maybe more is needed to
| > make sure a trace bit is not forgotten even if the macro is undefined.
| 
| That won't happen now (see the tests I committed).

Arg, we misunderstood each other, my bad :(

You successfully reimplemented the behavior of 1.4, which is insane
IMHO.  To me it is really a bug that the trace bit be attached to a
body instead of a name.

When I ask for -t define, I don't want to see m4_define.  That's why I
was referring to a list of names.

But I do agree there are clearly two viable semantics: tracing a name,
or tracing a body.

Today's situation is OK for Autoconf, which is the most important
thing.