<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div class="" style="word-wrap:break-word; line-break:after-white-space">Hi,
<div class=""><br class="">
</div>
<div class="">I've been looking at TDL reading in the LKB, and (partly for pragmatic reasons) I suggest restricting docstrings to occur only in the position immediately preceding the AVM - or just before the final . terminator if there is no AVM. Here are my
reasons:</div>
<div class=""><br class="">
</div>
<div class="">1. The LKB currently only allows docstrings in that position, and changing this while retaining backward compatibility would require an unreasonable amount of patching in a grammar lkb/patches.lsp file</div>
<div class="">2. This position is analogous to where docstrings are allowed in programming languages / docstring packages</div>
<div class=""><br class="">
</div>
<div class="">In the hope that this is acceptable, at least for the time being, I've sent Dan a new version of his patch to change docstrings from double-quoted to triple double-quoted in the LKB. The patch is attached in case other grammar developers want
to pick it up.</div>
<div class=""><br class="">
</div>
<div class="">John</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 7 Sep 2018, at 00:29, <a href="mailto:goodman.m.w@gmail.com" class="">
goodman.m.w@gmail.com</a> wrote:</div>
<br class="x_Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">Hi all,</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">There are some remaining issues with TDL that I'd like to clean up. First I will summarize some decisions made (or at least not rejected) in previous email threads:<br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">1. Supertypes appear before other terms in a conjunction only by convention (not enforced in the syntax)<br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">2. Docstrings are triple-quoted and may appear before any top-level term or before the final . terminator</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">3. Comments may appear in definitions anywhere that spaces can, except within strings/regexes/affixing-patterns</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">The following changes are things I think people agree with, so I'd like to consider them as decided:<br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">4. Removal of the :< operator (if accepted as a variant of :=, throw a warning)</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">5. Removal of 'single-quoted-symbols</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">6. Removal of double-quoted "docstrings"<br class="">
</div>
<div class="">
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">7. Removal of non-regex uses of ^ (otherwise any BNF of TDL is necessarily incomplete because the "extended-syntax" use of ^ is open-ended)<br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">And there's at least one point I don't think we reached a decision on:</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">8. Instances must have exactly 1 "supertype" (which is really just a type and not a supertype, i.e., it doesn't change the type hierarchy)<br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">Also:</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">9. Does anyone know how wild-cards differ from letter-sets? I see HaG has a wild-card and suffix pattern like these:</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"><br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"> %(wild-card (?g ui))</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"> ...<br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"> %suffix (!c!v !c!vn) (!v?g !vn)<br class="">
</div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif"></div>
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">My guess is that wild-cards match but are not used in the replacement, which I can imagine is useful if you want the replacement to use the second of two matches but not the first.
It makes me wonder why we don't just use regex substitutions for these things.<br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="x_gmail_default" style="font-family:arial,helvetica,sans-serif">If nobody responds about (1)--(7), I'll make sure the syntax description on the TdlRfc wiki reflects those decisions.</div>
<br class="">
</div>
-- <br class="">
<div dir="ltr" class="x_gmail_signature">-Michael Wayne Goodman</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<div class=""></div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">
<div class=""></div>
<div class=""><br class="">
</div>
</div>
</body>
</html>