Skip to content
Switch branches/tags

Latest commit

* Allow native-ftypes to work, even when a non-ftype is bound to the ftype name.

updated ftypes to allow native ftypes to be used even if another
non-ftype syntactic binding for the type exists.  for instance, if a
syntactic binding for integer-32 is introduced which is not bound to
an ftd, using integer-32 in the context of an ftype will still work.
this change also allows an ftype binding to be created for a native
type by using (define-ftype <native-type> <native-type>), allowing
users to create standard ftype bindings for the native-types if that
is preferred.

* Adding some tests for ftype changes.

Added a couple of tests for the ftype change to avoid having syntactic
bindings overlap the native ftype names without interfering with the
operation of ftype definitions.

This also includes a fix to the CSUG ftype section, thanks to Oscar
Waddell for the change.

* Small clarification on endianness in CSUG.

* Updated release notes to include note about ftype update.

* Added corrections suggested by @burgerrg

Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Chez Scheme is both a programming language and an implementation of that language, with supporting tools and documentation.

As a superset of the language described in the Revised6 Report on the Algorithmic Language Scheme (R6RS), Chez Scheme supports all standard features of Scheme, including first-class procedures, proper treatment of tail calls, continuations, user-defined records, libraries, exceptions, and hygienic macro expansion.

Chez Scheme also includes extensive support for interfacing with C and other languages, support for multiple threads possibly running on multiple cores, non-blocking I/O, and many other features.

The Chez Scheme implementation consists of a compiler, run-time system, and programming environment. Although an interpreter is available, all code is compiled by default. Source code is compiled on-the-fly when loaded from a source file or entered via the shell. A source file can also be precompiled into a stored binary form and automatically recompiled when its dependencies change. Whether compiling on the fly or precompiling, the compiler produces optimized machine code, with some optimization across separately compiled library boundaries. The compiler can also be directed to perform whole-program compilation, which does full cross-library optimization and also reduces a program and the libraries upon which it depends to a single binary.

The run-time system interfaces with the operating system and supports, among other things, binary and textual (Unicode) I/O, automatic storage management (dynamic memory allocation and generational garbage collection), library management, and exception handling. By default, the compiler is included in the run-time system, allowing programs to be generated and compiled at run time, and storage for dynamically compiled code, just like any other dynamically allocated storage, is automatically reclaimed by the garbage collector.

The programming environment includes a source-level debugger, a mechanism for producing HTML displays of profile counts and program "hot spots" when profiling is enabled during compilation, tools for inspecting memory usage, and an interactive shell interface (the expression editor, or "expeditor" for short) that supports multi-line expression editing.

The R6RS core of the Chez Scheme language is described in The Scheme Programming Language, which also includes an introduction to Scheme and a set of example programs. Chez Scheme's additional language, run-time system, and programming environment features are described in the Chez Scheme User's Guide. The latter includes a shared index and a shared summary of forms, with links where appropriate to the former, so it is often the best starting point.

Get started with Chez Scheme by Building Chez Scheme.

For more information see the Chez Scheme Project Page.