+The portable syntax-case macro system implements the restricted high-level +syntax-rules and equally high-level but general-purpose +syntax-case macros of the +Revised⁶ Report on Scheme (R6RS). +It also implements R6RS libraries and all built-in R6RS syntactic forms. + +

+The portable system is designed to be adaptable with minimal effort to +any R6RS or R5RS implementation of Scheme, with the +provision of a small set of implementation-dependent hooks. +Along with a reader, the system forms a complete front-end for Scheme. +If the reader and evaluator support source annotations (e.g., file +and line number information), these are handled as well to provide +source-object correlation. + +

+More information on the psyntax system and links to the implementation +can be found at Aziz Ghuloum's +psyntax page, +a backup copy of which is here. +The system was created by Abdulaziz Ghuloum and Kent Dybvig based on an +earlier implementation by Kent Dybvig, +Oscar Waddell, Bob Hieb, and Carl Bruggeman. + +

+ + + + + + + diff --git a/www/old-psyntax.html b/www/old-psyntax.html new file mode 100644 index 0000000..c305848 --- /dev/null +++ b/www/old-psyntax.html @@ -0,0 +1,545 @@ + + + + + +Pre-R6RS Portable syntax-case + + + +

Pre-R6RS Portable syntax-case

+The syntax-case macro system implements the restricted high-level +syntax-rules macros of the Revised⁵ Report +as well as the equally high-level but general-purpose +syntax-case macros. +It also supports a compatible module system that allows import and +export of macro bindings as well as bindings for variables and +modules. + +

+The portable system is designed to be adaptable with minimal effort to +any Revised⁵ Report implementation of Scheme, with the +provision of a small set of implementation-dependent hooks to install +the expander. +Included with the portable expander are definitions of each of the +syntactic forms supported by the Revised⁵ Report. +Along with a reader, the system forms a complete front-end for Scheme. +If the reader and evaluator support source annotations (e.g., file +and line number information), these are handled as well to provide +source-object correlation. + +

+The portable syntax-case implementation consists of one file, +psyntax.ss. +The file psyntax.pp is +an expanded version of the file that may be used for bootstrapping +the system. +See the porting notes in psyntax.ss + +

+Please let us know if you successfully port this code to a new Scheme +implementation, and also please allow us to include the hooks you +develop in doing the port in this directory for use by others. + +

+Please also contact us if you have difficulty porting to a new Scheme +implementation or if you discover that the implementation depends on +nonportable features of Chez Scheme in some undocumented way. + +

Release Notes

+Version numbers refer to the version of Chez Scheme from which the +portable version was extracted. + +

Version 7.3 (2/26/2007)

Version 7.1 (8/1/2006)

Version 7.0 (9/2/2005)

Version 6.9c (9/2/2004)

Version 6.9a (5/13/2003)

Version 6.9 (7/12/2002)

Version 6.8 (2/6/2002)

Version 6.3 (8/30/2000)

+ + + diff --git a/www/r6rs-libraries/index.html b/www/r6rs-libraries/index.html new file mode 100644 index 0000000..91477a5 --- /dev/null +++ b/www/r6rs-libraries/index.html @@ -0,0 +1,472 @@ + + + + +The portable R6RS library and syntax-case system + + + + +

+ +

psyntax

+ +

+ + + +

+ +

About psyntax

+ +

This page contains a reference implementation of the + proposed implicitly-phased libraries for R6RS. The + implementation is portable, depending only on a small set of + common primitives that are readily available in many + implementations. The implementation is also written as a + collection of R6RS libraries in order to take advantage of the + key R6RS libraries benefit: to easily isolate + implementation-dependent extensions in a mechanical way.

+ + + + + + +

Supported Platforms

+ +

The system is known to load and bootstrap itself properly + on the following Scheme implementations:

+ +

Bigloo 3.0b
Chez Scheme 7.2
Chicken 2.710
Gambit 4.0.1
Gauche 0.8.11
Ikarus (Build 2007-09-24)
Larceny 0.93
MIT-Scheme 7.7.90.+
MzScheme v371 [3m]
Petite Chez Scheme 7.2
Scheme48 1.7
SISC (1.16.6)

+ +

For every supported platform, there is a + "<impl>.r6rs.ss" + file containing a small number of compatibility definitions + that allow loading the expanded system (e.g. psyntax.pp) + properly.

+ +

To port to another system, start by loading "psyntax.pp". + If you get an error about undefined variables, look for how + these variables are defined in the other *.r6rs.ss files and + port them over to your implementation. It would help to start + with a supported implementation that's most familiar to you. + Please let me know (email: aghuloum at cs.indiana.edu) if you + get the system ported to another platform.

+ +

Downloads

+ +

+ Download + psyntax-r6rs-rev4.tgz + (released Oct 27, 2007). +

+ +

Older versions

psyntax-r6rs-rev1.tgz + released on Oct 3, 2007.

+ +

Development

+ + +

Development of the portable syntax-case system is + continuing. For the latest snapshot, and to submit bug reports + and feature requests, please visit: + Launchpad's + r6rs-libraries project.

+ +

Access to the latest development snapshot is through + Bazaar Version Control. + If you have bzr, you get the software by typing the + following command at your terminal: +

+  $ bzr branch http://bazaar.launchpad.net/~aghuloum/r6rs-libraries/r6rs-libraries.dev
+

+ + +

Basic Usage

+ + +

To run an r6rs script on your system, you'll need the + following files:

+ +

The script you want to run (say hello-world.ss).
The host.r6rs.ss file for your platform.
The pre-built/psyntax-host.pp file.

+ +

For example, we may have a script that looks like:

+ +

+         $ cat hello-world.ss 
+         (import (rnrs io simple))
+         (display "Hello World\n")
+

+ + +

We copy our host's pre-built/psyntax-host.pp to + psyntax.pp + For Petite Chez Scheme, we'd do:

+ +

+        $ cp pre-built/psyntax-petite.pp .
+

+ + +

Run your implementation's r6rs.ss file passing the + script name as an extra argument. For example, under petite, + we do:

+ +

+        $ petite --script petite.r6rs.ss hello-world.ss 
+        r6rs psyntax ready
+        Hello World
+

+ + +

If you want to write a library, say (my-library) as:

+ +

+        $ cat my-library.ss 
+        (library (my-library)
+          (export print-hello)
+          (import (rnrs))
+          (define (print-hello)
+             (display "Hello World\n")))
+

+ + +

And then write your hello-world.ss script as:

+ +

+        $ cat hello-world.ss 
+        (import (my-library))
+        (print-hello)
+

+ + +

Then, you can run it as before:

+ +

+        $ petite --script petite.r6rs.ss hello-world.ss 
+        r6rs psyntax ready
+        Hello World
+

+ + + +

The library system takes care of mapping the library names + that you import to file names via a primitive simple + mapping:

+ +

+       (foo)         =>    ./foo.ss
+       (foo bar)     =>    ./foo/bar.ss
+       ...
+

+ + +

To avoid any problems now, stick with names that contain + characters in [a..z], [A..Z], + [0..9], "-", "_", "~", and + ".". If you have ideas about a general + library-name->file-name mapping that you'd like to share, + please do email me.

+ + +

That's pretty much it as far as basic usage is concerned. + Let me know if you have any problems.

+ +

Structure of the system

+ +

Makefile Used to build the system under all supported + platforms.
README.txt The file you're reading right now.
psyntax-buildscript.ss + An r6rs script that's used to bootstrap the whole system.
*.r6rs.ss + Compatibility files for supported platforms with the exception of + kawa.r6rs.ss which is not working yet.
pre-built/*.pp + Pre-built expanded files for the supported platforms.
session-id + Used by gensym to generate unique ids across sessions.
examples hello-world.ss + Example scripts.
psyntax/internal.ss (psyntax internal)
+ Contains definitions of some internal procedures that are used by + the system but may need to be modified to get optimal performance + and usability on any platform. It is currently written as a + common-denominator of all supported platforms.
psyntax/builders.ss + (psyntax builders)
+ Exports procedures/macros that are used by the expander to build + the output expression. For example, build-letrec is used to build + letrec expressions. Implementations with tight integration may + replace the builders with constructors of compiler-internal data + structures.
psyntax/expander.ss + (psyntax expander)
+ The core of the expander.
psyntax/library-manager.ss + (psyntax library-manager)
+ The library manager keeps track of what libraries are installed + and available on the system. It takes care of visiting/invoking + such libraries as well as loading them from source files.
psyntax/config.ss + (psyntax config)
+ This is a compile-time configuration file for determining what + forms the implementation supports (e.g. is case-lambda supported + or should it be expanded). The provided configuration is one that + works for all implementation (common denominator).
psyntax/compat.ss + (psyntax compat)
+ This is a compatibility file for some non-r6rs forms that are used + in other libraries but can be implemented portably in terms of + other r6rs features. make-parameter, parameterize, and + define-record.
psyntax/main.ss + (psyntax main)
+ This library is the main entry point to the r6rs world. It + prints a greeting message and processes the file given in the + command line argument as an r6rs-script.

+ +

Non-R6RS requirements

+ +

void: The procedure void is used in the output of the + expander when we don't care about a value (e.g. to provide the + initial values for the letrec*/internal-defines). A call + to void should not signal any errors. (define (void) (if #f + #f)) suffices for this purpose.

+ + +

pretty-print: The procedure pretty-print should take + one or two values: an expression (code) to be printed and, + optionally, an output port. It should pretty-print the code to that + port (or the current-output-port if a port is not provided. + Implementations with no pretty printer can (define pretty-print + write) for this purpose but the output won't be very + readable.

+ +

eval-core: This procedure should take a core s-expression and + evaluate it in a "top-level" environment. R5RS implementations can + define it as

+(define (eval-core x) (eval x (interaction-environment)))
+

+ + +

gensym: The procedure gensym should create a globally unique symbol + with read/write invariance. It is used to create unique locations + for exported identifiers, unique names for lexical variables, and + unique labels in the expand-time environment. Of the supported + Scheme implementations, only Chez Scheme and Ikarus provide a usable + gensym implementation for this purpose; yet their printed + represenation of gensyms are not portable (cannot be read by the + other R5RS implementations). For this, we provide a gensym + implementation that's semi portable but relies on an external state + (session-id file) to ensure that the sequence of symbols generated + are unique across sessions. Gensym takes an optional argument that + is either a string or a symbol that can be used to correlate the + source name of the identifier with its unique name. The output of + our implementation of gensym looks like

+    <name>$<session-id>$<gensym-id>
+

+ where both session-id and gensym-id are nonnegative integers. + +

symbol-value: This procedure takes a symbol + (typically a gensym) and returns the value associated with it + in the global environment. The symbol is guaranteed to be + initialized either via a global define or via + set-symbol-value! (below).

+ +

set-symbol-value!: This procedure takes a symbol + (typically a gensym) and a value and associates the value with + the symbol in the global environment (in a way that eval-core + can properly see it).

+ + + +

Changes

+ +

Oct 27, 2007: + All of R6RS core syntactic forms are now supported by the + expander including define-record-type, + record-type-descriptor, + record-constructor-descriptor, + define-condition-type, define-enumeration, + and guard. + The expander now parses and enforces + version and subversion requirements for imported libraries. + The initial library set have proper version names, + (6). +
Oct 3, 2007: Initial release (at ICFP 2007). + Implements most of the core functionality of R6RS including + the expander and the library manager.

+ +

License

+ +

The following license applies to all of the distributed + psyntax files:

+ +

+Copyright (c) 2006, 2007 Abdulaziz Ghuloum and Kent Dybvig
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation files
+(the "Software"), to deal in the Software without restriction,
+including without limitation the rights to use, copy, modify, merge,
+publish, distribute, sublicense, and/or sell copies of the Software,
+and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
+BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
+ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

+ + +

+spec	$<graphic>$	id
+	\|	`(only` spec id*`)`
+	\|	`(except` spec id*`)`
+	\|	`(add-prefix` spec id`)`
+	\|	`(drop-prefix` spec id`)`
+	\|	`(rename` spec (new-id old-id)*`)`
+	\|	`(alias` spec (new-id old-id)*`)` +