Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Looks ok; except that I can even find usage of _AC_EVAL out in the wild: > http://www.berenddeboer.net/eiffel/eiffel.m4 sigh.
Well, that use shouldn't be a problem, since _AC_EVAL has gone back to the old meaning. If you can find _AC_EVAL_STDERR in the wild, that would be a problem, as it's no longer present. We could easily fix that by putting _AC_EVAL_STDERR in with its old meaning. On the other hand one has to draw the line somewhere; these macros are clearly marked to be internal. By the way, how do you find these wild uses so easily?
