I changed it to `m4wrap can be called from m4wrapped text. However, the order of evaluation can not be determined ahead of time.'
I've attached a diff to m4.texinfo, if that is correct. Samuel Lauber ----- Original Message ----- From: "Stepan Kasal" <[EMAIL PROTECTED]> > Hello, > > [the best place to discuss m4 bugs is bug-m4, so I'm moving the > discussion there] > > On Sun, Jan 09, 2005 at 07:38:26PM +0100, Sam Lauber wrote: > > "It is safe to call `m4wrap' from saved text, but the order in > > which the saved text is read is undefined." > > > > I do not understand that paragraph, and I think it should be > > changed to a more understandable form. > > I think I understand it: > 1) it's not an error to call m4wrap in the text saved by m4wrap. > 2) the text will be read back before m4 exits, but you cannot say when; > it may be after all other texts saved by m4wrap so far, or between two > of them; I suppose that no text saved by m4wrap will be interrupted by > another text saved this way. > > Well, I see now that this formulation leaves space for various > interpretation. > > Thank you for reporting this problem. If you have capacities to help > even more, you could perhaps suggest an explanation. The developers > would check that it describes what they meant to promise, and update > the documentation. > > Thanks, > Stepan Kasal -- _____________________________________________________________ Web-based SMS services available at http://www.operamail.com. From your mailbox to local or overseas cell phones. Powered by Outblaze
m4-doc.diff
Description: Binary data
_______________________________________________ Bug-m4 mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-m4
