* Eric Blake wrote on Mon, Jun 19, 2006 at 02:30:12PM CEST: > According to Paul Eggert on 6/19/2006 12:33 AM: > > > > One possibility for m4wrap is to do nothing until after 2.60 is out. > > I.e., if m4 2.0 isn't expected to be out soon, we can fix m4wrap > > issues in Autoconf 2.61. > > I'll put it this way. If 2.60 adds an m4wrap workaround, then m4 2.0 > might come out before autoconf 2.61. But if 2.60 does not add an m4wrap > workaround, then m4 development will have to wait for yet another autoconf > release.
Nono, let's fix the issue now. I think we can take Stepan's patch. I'll try to write down tonight why I think we can do this, and why I think it's preferable over your (Eric's) latest patch variant, although (off-list) Stepan was giving in and trying to convince me to prefer Eric's over his. :-) Cheers, Ralf _______________________________________________ Bug-m4 mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-m4
