--- Begin Message ---
Subject: |
Re: noweb: unclosed module name |
Date: |
Tue, 20 Dec 2005 17:52:44 -0500 |
> Dear Norman,
>
> I think, I have found the problem in markup.nw.
Thanks for prodding me on this.
Enclosed find a patch, which will become part of noweb 2.11.
Norman
===================================================================
RCS file: RCS/markup.nw,v
retrieving revision 2.17
diff -r2.17 markup.nw
25c25
< static char rcsname[] = "$Name: $";
---
> static char rcsname[] = "$Name: v2_10c $";
150c150,154
< beginning of a code chunk is easy.
---
> beginning of a code chunk is easy. The only tricky bit is that if we
> see an unclosed, unescaped [[<<]] in a code chunk, this should be acceptable.
> Because in a documentation chunk, an unclosed, unescaped [[<<]] will
> already be caught with a ``module name doesn't end'' message, the
> right thing to do here is silently to let an unclosed [[<<]] pass.
161,162c165
< if (tail == NULL) <<error exit from [[starts_code]]>>
< if (*tail++ != '=') return 0;
---
> if (tail == NULL || *tail++ != '=') return 0;
178,182d180
< <<error exit from [[starts_code]]>>=
< {
< errorat(filename, lineno, Error, "Module name doesn't end", line);
< return 0;
< }
--- End Message ---