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

[Akim Demaille]

>>>>> "Gary" == Gary V Vaughan <address@hidden> writes:

Gary> I'll look at this properly after the weekend when my chapter is
Gary> done.  In the mean time, do you think that there is a genuine
Gary> need to track the traced flag on each `struct m4_token_data'
Gary> *and* each symbol name?

Well, I reversed the patch we are debating about, and nothing changes,
it's coming from another one.

I definitely understand your point, but at the origin that was the
guarantee that you could follow a builtin even if renamed (define +
defn).

Today, I am more and more convinced that what would be really clean is
simply a list of macros to be traced, and each time a macro is
defined, we look at this list.

I.e., if I `m4 -t foo', then, what ever the number of define and
undefine of foo, all invocation of the macro should be traced.

Up to now, only the invocations before the first undefine are traced.
This is really what I'm looking for, and it is also what I consider as
the sanest semantics for traces.