Recent changes to Home

Home modified by David A. Wheeler

David A. Wheeler — Fri, 31 Oct 2014 21:37:19 -0000

--- v92
+++ v93
@@ -14,7 +14,9 @@

 These are just *additional* *abbreviations* - normally-formatted s-expressions continue to work correctly.

-You do *not* need to use all three tiers.  You could use neoteric-expressions, for example, which automatically include c-expressions.  Here's s one of our [Examples] of sweet-expressions (the top tier):
+You do *not* need to use all three tiers.  You could use neoteric-expressions, for example, which automatically include c-expressions.
+
+Here's one of our [Examples] of sweet-expressions (the top notation tier):

Home modified by David A. Wheeler

David A. Wheeler — Fri, 31 Oct 2014 21:02:22 -0000

--- v91
+++ v92
@@ -4,15 +4,17 @@

 The [Problem] is that traditional Lisps don't support infix notation, don't support the standard math notation f(...), and require an excessive number of parentheses.  Our [Solution] has three tiers that add additional *abbreviations* to existing Lisp readers.  Put briefly:

-1.  *Curly-infix-expressions* (*c-expressions*): Lists surrounded by {...} are interpreted as infix notation, in a Lispy way.
-2.  *Neoteric-expressions* (*n-expressions*): An e(...) is interpreted as (e ...), an e{...} is interpreted as (e {...}).
+1.  *Curly-infix-expressions* (*c-expressions*): Lists surrounded by {...} are interpreted as infix notation, in a Lispy way.  For example, {a + b} represents (+ a b).
+2.  *Neoteric-expressions* (*n-expressions*): An e(...) is interpreted as (e ...), an e{...} is interpreted as (e {...}).  For example, sin(x) represents (sin x).
 3.  *Sweet-expressions* (*t-expressions*): Parentheses are deduced from indentation:
     - An indented line is a parameter of its parent.
     - Later terms on a line are parameters of the first term.
     - A line with exactly one term and no child lines is simply that term.
     - Empty lines end the previous expression. Just type ENTER ENTER to execute what you've typed.

-These are just *additional* *abbreviations* - normally-formatted s-expressions continue to work correctly.  Here's one of our [Examples]:
+These are just *additional* *abbreviations* - normally-formatted s-expressions continue to work correctly.
+
+You do *not* need to use all three tiers.  You could use neoteric-expressions, for example, which automatically include c-expressions.  Here's s one of our [Examples] of sweet-expressions (the top tier):

Home modified by David A. Wheeler

David A. Wheeler — Sat, 18 Oct 2014 17:22:02 -0000

--- v90
+++ v91
@@ -76,4 +76,4 @@
 # Join us!

 [Join] - Please join us!
-[Workflow] - Information on our workflow.
+[Workflow] - Information on our workflow (esp. moving information from the "develop" development branch to the "master" release branch)

Home modified by David A. Wheeler

David A. Wheeler — Sat, 18 Oct 2014 17:20:46 -0000

--- v89
+++ v90
@@ -62,7 +62,7 @@

 # Download Releases

-[The "releases" (files) area distributes our software releases for download](https://sourceforge.net/projects/readable/files/).  The README describes how to install them; they install using usual conventions and include documentation.
+[The "releases" (files) area distributes our software releases for download](https://sourceforge.net/projects/readable/files/).  The README describes how to install them; they install using usual conventions and include documentation.  This reflects the latest version on the "master" branch.

 Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.  The easy way to start contributing code is to select the "develop" branch (not the "master" branch) and fork it; when you're done, submit a push request.  If you want to get the development code using the command line, and give it a go, do this:

@@ -76,3 +76,4 @@
 # Join us!

 [Join] - Please join us!
+[Workflow] - Information on our workflow.

Home modified by David A. Wheeler

David A. Wheeler — Sun, 22 Jun 2014 19:19:25 -0000

--- v88
+++ v89
@@ -64,7 +64,14 @@

 [The "releases" (files) area distributes our software releases for download](https://sourceforge.net/projects/readable/files/).  The README describes how to install them; they install using usual conventions and include documentation.

-Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.  The easy way to start contributing code is to select the "develop" branch (not the "master" branch) and fork it; when you're done, submit a push request.
+Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.  The easy way to start contributing code is to select the "develop" branch (not the "master" branch) and fork it; when you're done, submit a push request.  If you want to get the development code using the command line, and give it a go, do this:
+
+

+     git clone git://git.code.sf.net/p/readable/code readable-code
+     cd readable-code
+     git checkout -b develop origin/develop  # Set up and switch to "develop" branch
+     autoreconf -i && ./configure --prefix=/usr && make
+

# Join us!

Home modified by David A. Wheeler

David A. Wheeler — Sat, 14 Jun 2014 13:10:29 -0000

--- v87
+++ v88
@@ -49,6 +49,7 @@
 * [Common-lisp-tutorial] - a tutorial on how to try it out (Common-Lisp-focused)
 * [Style] - style guide for using them
 * [Examples] - examples of code using these formats
+* [Prepackaged] - list of (some) places where these are pre-packaged
 * [Home] - Readable Lisp project's Wiki home

 # Philosophy behind the Readable project

Home modified by David A. Wheeler

David A. Wheeler — Fri, 27 Sep 2013 01:15:57 -0000

--- v86
+++ v87
@@ -44,6 +44,7 @@
 * [Solution] - a more detailed description of our solution
     * [SRFI-105](http://srfi.schemers.org/srfi-105/srfi-105.html) - a formal request to implement our infix notation, for Scheme.  Note that guile now includes this.
     * [SRFI-110](http://srfi.schemers.org/srfi-110/srfi-110.html) - a formal request to implement our sweet-expression (indentation) format, for Scheme.
+* [Install-howto] - how to install it
 * [Scheme-tutorial] - a tutorial on how to try it out (Scheme-focused)
 * [Common-lisp-tutorial] - a tutorial on how to try it out (Common-Lisp-focused)
 * [Style] - style guide for using them

Home modified by David A. Wheeler

David A. Wheeler — Sun, 25 Aug 2013 16:50:24 -0000

--- v85
+++ v86
@@ -62,7 +62,7 @@

 [The "releases" (files) area distributes our software releases for download](https://sourceforge.net/projects/readable/files/).  The README describes how to install them; they install using usual conventions and include documentation.

-Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.  The easy way to start contributing code is to select the "develop" branch and fork it; when you're done, submit a push request.
+Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.  The easy way to start contributing code is to select the "develop" branch (not the "master" branch) and fork it; when you're done, submit a push request.

 # Join us!

Home modified by David A. Wheeler

David A. Wheeler — Sun, 25 Aug 2013 16:49:31 -0000

--- v84
+++ v85
@@ -62,7 +62,7 @@

 [The "releases" (files) area distributes our software releases for download](https://sourceforge.net/projects/readable/files/).  The README describes how to install them; they install using usual conventions and include documentation.

-Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.
+Our draft (development) code is in the [readable code git repository](https://sourceforge.net/p/readable/code) "develop" branch; see [Workflow] for information on our workflow.  The easy way to start contributing code is to select the "develop" branch and fork it; when you're done, submit a push request.

 # Join us!

Home modified by David A. Wheeler

David A. Wheeler — Tue, 07 May 2013 01:49:41 -0000

--- v83
+++ v84
@@ -44,7 +44,6 @@
 * [Solution] - a more detailed description of our solution
     * [SRFI-105](http://srfi.schemers.org/srfi-105/srfi-105.html) - a formal request to implement our infix notation, for Scheme.  Note that guile now includes this.
     * [SRFI-110](http://srfi.schemers.org/srfi-110/srfi-110.html) - a formal request to implement our sweet-expression (indentation) format, for Scheme.
-* [Tutorial] - a tutorial on how to try it out
 * [Scheme-tutorial] - a tutorial on how to try it out (Scheme-focused)
 * [Common-lisp-tutorial] - a tutorial on how to try it out (Common-Lisp-focused)
 * [Style] - style guide for using them