| From: Akim Demaille <[EMAIL PROTECTED]>
| Date: 14 Feb 2000 10:43:04 +0100
|
| s/^m4trace:\([^:]*\):\([^:]*\): -[0-9]*- \([^(]*(\)\(.*\)$/\3[\1], [\2], \4/
|
| This looks like a good idea to me. I would improve it slightly by
| making it more specific, e.g.
|
| s/^m4trace:\([^:][^:]*\):\([0-9][0-9]*\): -[0-9][0-9]*-
|\([A-Z_a-z][0-9A-Z_a-z]*(\)\(.*\)$/\3[\1], [\2], \4/
Wow, thanks :) I will also adapt it for the case where there are no
() (because m4 doesn't output them in this case).
| Now if this idea is accepted, the question will be that of the format
| of the request. It can be directly the definition in m4,
|
| autoconf --trace AC_SUBST($1:$3)
|
| to ask just for the line number and the variable, separated with a colon.
|
| This sounds good, but I didn't follow that example. Why is $1 the
| line number and $3 the variable?
As Alexandre pointed out, it should be hidden from the user, but
internally, because we re-feed m4 after having added new parameters
(line number, file name etc.), there's a shift. We could just leave
them before, but the point is to give the control over their output.
Akim
