<div dir="ltr">On Sat, Sep 6, 2008 at 12:46 AM, Matthew Fluet <span dir="ltr"><<a href="mailto:fluet@tti-c.org">fluet@tti-c.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would make the syntax for an mlb-path-map path the same as an mlb path:<br>
<br>
Paths may include path variables and are expanded according to a path<br>
map. Unquoted paths may include alpha-numeric characters and the<br>
symbols "-" and "_", along with the arc separator "/" and extension<br>
separator ".". More complicated paths, including paths with spaces, may<br>
be included by quoting the path with ". A quoted path is lexed as an SML<br>
string constant.<br>
<br>
That is, if we let [[:file:]] denote the epoynmous regexp from <src>/front-end/mlb.lex and let [[:smlstring:]] be a regexp for SML string constants, then an mlb-path-map entry line could be taken by the regexp:<br>
<br>
^[[:space:]]*\([A-Z_][A-Z0-9_]*\)[[:space:]]+\([[:file:]]\|[[:smlstring:]]\)[[:space:]]$</blockquote><div class="Ih2E3d"><br>This does seem better than my proposal.<br><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It would probably be useful to allow comments in a mlb-path-map file.<br>
</blockquote>
</div><br>As normal SML-style comments then?<br><br>Of course, it turns the 3-line code there is now into yet another lexer.<br><br></div></div>