than `nn', so that `nnn' is valid in warnings.
Reported by Steve Huston.
+2003-10-31 Akim Demaille <akim@epita.fr>
+
+ * bin/autom4te.in (&freeze): Use a less likely warning separator
+ than `\n\n', so that `\n\n\n' is valid in warnings.
+ Reported by Steve Huston.
+
2003-10-28 Akim Demaille <akim@epita.fr>
* Makefile.cfg (local_updates, executable-update): Tweak to be
Simon Leinen simon@lia.di.epfl.ch
Stephen Gildea filtered@against.spam
Steve Chamberlain sac@cygnus.com
-Steven G. Johnson stevenj@alum.mit.edu
+Steve Huston shuston@riverace.com
Steve Robbins steve@nyongwa.montreal.qc.ca
+Steven G. Johnson stevenj@alum.mit.edu
Stu Grossman grossman@cygnus.com
Syd Polk spolk@cygnus.com
T.E. Dickey dickey@clark.net
if $force || ! $req->valid;
# Issue the warnings each time autom4te was run.
+my $separator = "\n" . ('-' x 25) . " END OF WARNING " . ('-' x 25) . "\n\n";
handle_traces ($req, "$tmp/warnings",
- ('_m4_warn' => "\$1::\$f:\$l::\$2::\$3\n\n"));
-# Warnings are separated by 2 \n.
-for (split (/\n{2,}/, contents ("$tmp/warnings")))
+ ('_m4_warn' => "\$1::\$f:\$l::\$2::\$3$separator"));
+# Swallow excessive newlines.
+for (split (/\n*$separator\n*/o, contents ("$tmp/warnings")))
{
# The message looks like:
# | syntax::input.as:5::ouch