<sigh> sorry David I just keep pressing the wrong button...
---------- Forwarded message ---------- From: Alan Manuel Gloria <[EMAIL PROTECTED]> Date: Dec 19, 2007 11:59 PM Subject: Re: [Readable-discuss] Maybe index non-default is better after all! To: [EMAIL PROTECTED] On Dec 9, 2007 1:21 PM, David A. Wheeler <[EMAIL PROTECTED]> wrote: > Here are the current rules for draft 0.2 of sweet-expressions, as shown in: > http://www.dwheeler.com/readable/version02.html > I'd love to hear feedback! Looks pretty good, although I'm kind of confused in your ACL2 example - is the syntax for nonpunctuation infix {x implies b} or {a /implies/ b}? Or does {} automatically assume that if the second entry in a 3-entry list is a symbol (regardless of punctuation or lack thereof) it must be infix (for non-infixed default)? > 6. Immediate completion. A single complete expression that begins at the > left edge of a line, and is immediately followed by newline after it > completes, causes the expression to immediately complete (without waiting for > the next line of input). ‣ Thus, entering load("hello") and immediately > pressing return will execute immediately, but load "hello" will require > pressing Enter twice (because there might be another line to follow). This > rule makes interactive use more pleasant, without harming file reading. It > avoids two problems: (1) having to press Enter twice to execute simple > one-line commands, and (2) allowing the command line to easily go "out of > sync" (when, after pressing return, the user sees the result of the previous > line). Type an initial space if you want to enter only a single complete > expression on a line yet follow it with child lines. Hmm, this seems to conflict with your BitC example: deftypeclass forall (Eql('a)) Ord('a) < : fn(('a 'a) 'a) So: does deftypeclass have a starting space or no? And why not? Hmm, come to think of it this rule is kinda confusing to me... Sincerely, AmkG
