Recent changes to Names

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Sun, 19 Aug 2012 13:41:49 -0000

--- v7
+++ v8
@@ -21,6 +21,5 @@
 *   Escaping: {e} maps to e, because it "escapes" symbol e.
 *   Unary: {op e} maps to (op e), for any "op" and "e", because it lets you do {- x} and similar.
 *   Simple: {e1 op e2 op ...} maps to (even-parameter odd-parameters), this lets you do simple infix.
-*   Mixed: The rest, it has different operators mixed together.
+*   Mixed: The rest, it has different operators mixed together. Gets "nfx" put in front.  (A future version could add [Precedence] support for mixed notation, but that's not the current focus.)
 
-

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Sun, 19 Aug 2012 13:39:28 -0000

--- v6
+++ v7
@@ -13,6 +13,8 @@
 *   Neoteric-expressions, aka n-expressions.  These used to be called "modern-expressions".
 *   Sweet-expressions, aka t-expressions.
 
+The latter three are described in [Solution].
+
 Names for types of curly-infix formats (0.5):
 
 *   Empty: {} maps to (), because it's an empty list.
@@ -22,4 +24,3 @@
 *   Mixed: The rest, it has different operators mixed together.
 
 
-The latter three are described in [Solution].

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Sun, 19 Aug 2012 13:39:15 -0000

--- v5
+++ v6
@@ -13,4 +13,13 @@
 *   Neoteric-expressions, aka n-expressions.  These used to be called "modern-expressions".
 *   Sweet-expressions, aka t-expressions.
 
+Names for types of curly-infix formats (0.5):
+
+*   Empty: {} maps to (), because it's an empty list.
+*   Escaping: {e} maps to e, because it "escapes" symbol e.
+*   Unary: {op e} maps to (op e), for any "op" and "e", because it lets you do {- x} and similar.
+*   Simple: {e1 op e2 op ...} maps to (even-parameter odd-parameters), this lets you do simple infix.
+*   Mixed: The rest, it has different operators mixed together.
+
+
 The latter three are described in [Solution].

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Mon, 06 Aug 2012 10:30:06 -0000

--- v4
+++ v5
@@ -7,7 +7,7 @@
 The various notations we discuss are:
 
 *   S-expressions aka "traditional" S-expressions.  This is the traditional notation for Lisp-like languages for expressing underlying data structures.
-*   M-expressions.  This was an historic Algol-like notation created by John McCarthy for Lisp programs when Lisp was first created.  It was designed to be readable, but it wasn't homoiconic or general, so it never really got anywhere.  We're trying to do better, now that we know what the problem with it was.
+*   M-expressions.  This was an historic Algol-like notation created by John McCarthy for Lisp programs when Lisp was first created.  It was designed to be readable, but it wasn't homoiconic or general, so it never really got anywhere.  We're trying to do better, now that we know why it failed.
 *   I-expressions, aka SRFI-49.  This was the indentation format defined in SRFI-49, and was the starting point for the sweet-expression indent rules (though we've changed things).
 *   Curly-infix-expressions, aka c-expressions.
 *   Neoteric-expressions, aka n-expressions.  These used to be called "modern-expressions".

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Mon, 30 Jul 2012 01:43:35 -0000

--- v3
+++ v4
@@ -14,5 +14,3 @@
 *   Sweet-expressions, aka t-expressions.
 
 The latter three are described in [Solution].
-
-A current naming problem is *what* to name the module that implements readers for all of c-expressions, n-expressions, and t-expressions.

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Mon, 30 Jul 2012 01:42:45 -0000

--- v2
+++ v3
@@ -8,6 +8,7 @@
 
 *   S-expressions aka "traditional" S-expressions.  This is the traditional notation for Lisp-like languages for expressing underlying data structures.
 *   M-expressions.  This was an historic Algol-like notation created by John McCarthy for Lisp programs when Lisp was first created.  It was designed to be readable, but it wasn't homoiconic or general, so it never really got anywhere.  We're trying to do better, now that we know what the problem with it was.
+*   I-expressions, aka SRFI-49.  This was the indentation format defined in SRFI-49, and was the starting point for the sweet-expression indent rules (though we've changed things).
 *   Curly-infix-expressions, aka c-expressions.
 *   Neoteric-expressions, aka n-expressions.  These used to be called "modern-expressions".
 *   Sweet-expressions, aka t-expressions.

WikiPage Names modified by Alan Manuel Gloria

Alan Manuel Gloria — Thu, 26 Jul 2012 03:09:49 -0000

--- v1
+++ v2
@@ -14,3 +14,4 @@
 
 The latter three are described in [Solution].
 
+A current naming problem is *what* to name the module that implements readers for all of c-expressions, n-expressions, and t-expressions.

WikiPage Names modified by David A. Wheeler

David A. Wheeler — Mon, 23 Jul 2012 13:22:17 -0000

Here are the meanings of some terms, to reduce confusion. This overall project is the "Readable Lisp S-expressions" project, or the "readable" project for short. The mailing list we use is called "readable-discuss". Our wiki is just the "readable wiki", the git repository is just the "readable git repository". The various notations we discuss are: * S-expressions aka "traditional" S-expressions. This is the traditional notation for Lisp-like languages for expressing underlying data structures. * M-expressions. This was an historic Algol-like notation created by John McCarthy for Lisp programs when Lisp was first created. It was designed to be readable, but it wasn't homoiconic or general, so it never really got anywhere. We're trying to do better, now that we know what the problem with it was. * Curly-infix-expressions, aka c-expressions. * Neoteric-expressions, aka n-expressions. These used to be called "modern-expressions". * Sweet-expressions, aka t-expressions. The latter three are described in [Solution].