<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:times new roman,serif;font-size:large"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Sep 11, 2021 at 4:56 PM Eric Timmons <<a href="mailto:etimmons@mit.edu" target="_blank">etimmons@mit.edu</a>> wrote:</div><div dir="ltr" class="gmail_attr"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
colonsym = ':' | signsym<br></blockquote><div><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">Definitely a thinko on my part: fixed.</div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The implementations<br>
all seem to treat the character sequences #\\ #\n and #\\ #\t as<br>
#\Newline and #\Tab, respectively.</blockquote><div><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">Other people's thinkos: the spec prevails. If you could make a PR for the CL version to eliminate them, that would be handy.</div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Additionally a #\\ not followed by an<br>
#\n #\t #\" or #\\ will signal an error. </blockquote><div><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">I think it's appropriate to signal an error on every backslash not followed by a quote or another backslash, as they are POSE syntax violations, just as a stray ) or a # outside a string would be.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Third, I'm not sure how to deal with the case sensitivity of symbols. Is<br>
there any plan to add a :case argument or similar to POSE:READ? <br></blockquote><div><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large">The problem is deeper than that: if CL's POSE parser receives (Foo foo), it will lose the distinction. I am arguing (in #s-expressions in the libera.chat IRC network, if you want to join in) that since symbols are basically labels for things, we don't really lose anything by making them case insensitive.</div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br></div></div></div>