The Racket repository
Go to file
dybvig 48db0a9405 various library-manager improvements including the ability to verify
loadability without actually loading; also, support for unregistering
guarded objects.
- improved error reporting for library compilation-instance errors:
  now including the name of the object file from which the "wrong"
  compilation instance was loaded, if it was loaded from (or compiled
  to) an object file and the original importing library, if it was
  previously loaded from an object file due to a library import.
    syntax.ss, 7.ss, interpret.ss,
    8.ms, root-experr*
- removed situation and for-input? arguments from $make-load-binary,
  since the only consumer always passes 'load and #f.
    7.ss,
    scheme.c
- $separate-eval now prints the stderr and stdout of the subprocess
  to help in diagnosing separate-eval and separate-compile issues.
    mat.ss
- added unregister-guardian, which can be used to unregister
  the unressurected objects registered with any guardian.  guardian?
  can be used to distinguish guardian procedures from other objects.
    cp0.ss, cmacros.ss, cpnanopass.ss, ftype.ss, primdata.ss,
    prims.ss,
    gcwrapper.c, prim.c, externs.h,
    4.ms, primvars.ms
    release_notes.stex
    smgmt.stex, threads.stex
- added verify-loadability.  given a situation (visit, revisit,
  or load) and zero or more pathnames (each of which may be optionally
  paired with a library search path), verity-loadability checks
  whether the set of object files named by those pathnames and any
  additional object files required by library requirements in the
  given situation can be loaded together.  it raises an exception
  in each case where actually attempting to load the files would
  raise an exception and additionally in cases where loading files
  would result in the compilation or loading of source files in
  place of the object files.  if the check is successful,
  verity-loadability returns an unspecified value.  in either case,
  although portions of the object files are read, none of the
  information read from the object files is retained, and none of
  the object code is read, so there are no side effects other than
  the file operations and possibly the raising of an exception.
  library and program info records are now moved to the top of each
  object file produced by one of the file compilation routines,
  just after recompile info, with a marker to allow verity-loadability
  to stop reading once it reads all such records.  this change is
  not entirely backward compatible; the repositioning of the records
  can be detected by a call to list-library made from a loaded file
  before the definition of one or more libraries.  it is fully
  backward compatible for typical library files that contain a
  single library definition and nothing else.  adding this feature
  required changes to the object-file format and corresponding
  changes in the compiler and library manager.  it also required
  moving cross-library optimization information from library/ct-info
  records (which verity-loadability must read) to the invoke-code
  for each library (which verity-loadability  does not read) to
  avoid reading and permanently associating record-type descriptors
  in the code with their uids.
    compile.ss, syntax.ss, expand-lang.ss, primdata.ss, 7.ss,
    7.ms, misc.ms, root-experr*, patch*,
    system.stex, release_notes.stex
- fixed a bug that bit only with the compiler compiled at
  optimize-level 2: add-library/rt-records was building a library/ct-info
  wrapper rather than a library/rt-info wrapper.
    compile.ss
- fixed a bug in visit-library that could result in an indefinite
  recursion: it was not checking to make sure the call to $visit
  actually added compile-time info to the libdesc record.  it's not
  clear, however, whether the libdesc record can be missing
  compile-time information on entry to visit-library, so the code
  that calls $visit (and now checks for compile-time information
  having been added) might not be reachable.  ditto for
  revisit-library.
    syntax.ss
    syntax.ss, primdata.ss,
    7.ms, root-experr*, patch*,
    system.stex, release_notes.stex
- added some argument-error checks for library-directories and
  library-extensions, and fixed up the error messages a bit.
    syntax.ss,
    7.ms, root-experr*
- compile-whole-program now inserts the program record into the
  object file for the benefit of verify-loadability.
    syntax.ss,
    7.ms, root-experr*
- changed 'loading' import-notify messages to the more precise
  'visiting' or 'revisiting' in a couple of places.
    syntax.ss,
    7.ms, 8.ms

original commit: b911ed47190727b0e1d6a88c0e473d1757accdcd
2020-01-23 10:43:17 -08:00
.travis add Windows builds and update Linux dist to xenial 2019-04-24 13:21:03 -04:00
bintar install a file containing revision control information alongside boot files 2019-03-27 12:42:28 -04:00
c various library-manager improvements including the ability to verify 2020-01-23 10:43:17 -08:00
csug various library-manager improvements including the ability to verify 2020-01-23 10:43:17 -08:00
examples Updated csug socket code to match that in examples folder 2018-06-18 09:28:53 -04:00
lz4@c438548312 Add LZ4 support and use it by default for compressing files 2019-04-06 07:32:37 +02:00
makefiles Various enhancements and fixes highlighted by profiling performance 2019-09-21 15:37:29 -07:00
mats various library-manager improvements including the ability to verify 2020-01-23 10:43:17 -08:00
nanopass@1f7e80bcff latest nanopass 2016-06-27 09:45:20 -04:00
pkg fixed welcome text and copyright year in macOS package 2019-03-25 11:54:24 -04:00
release_notes various library-manager improvements including the ability to verify 2020-01-23 10:43:17 -08:00
rpm Now opening 9.5.3 release. Intent is to formally release 9.5.2 2019-03-21 15:07:39 -07:00
s various library-manager improvements including the ability to verify 2020-01-23 10:43:17 -08:00
stex@3bd2b86cc5 - compile-whole-program and compile-whole-library now copy the hash-bang 2016-05-04 20:35:38 -04:00
unicode initial upload of open-source release 2016-04-26 10:04:54 -04:00
wininstall Added support for building chez with VS2019. (#435) 2019-06-04 16:37:57 -04:00
zlib@cacf7f1d4e updated zlib to latest version, version 1.2.11 2017-02-13 22:27:21 -05:00
.gitattributes Adding .gitattributes files to correct language stats 2016-10-12 11:47:53 -04:00
.gitignore Added generated docs and intermediate files to .gitignore 2017-10-14 12:32:44 -04:00
.gitmodules Add LZ4 support and use it by default for compressing files 2019-04-06 07:32:37 +02:00
.travis.yml Travis: use bionic dist 2019-10-21 13:15:41 -04:00
BUILDING Fix typos 2019-08-10 18:34:21 +02:00
CHARTER.md initial upload of open-source release 2016-04-26 10:04:54 -04:00
checkin compress-level parameter, improvement in lz4 compression, and various other related improvements 2019-04-18 05:47:19 -07:00
configure Various enhancements and fixes highlighted by profiling performance 2019-09-21 15:37:29 -07:00
CONTRIBUTING.md - added custom install options. workarea creates an empty config.h, 2016-05-06 18:30:06 -04:00
LICENSE initial upload of open-source release 2016-04-26 10:04:54 -04:00
LOG various library-manager improvements including the ability to verify 2020-01-23 10:43:17 -08:00
newrelease fixed welcome text and copyright year in macOS package 2019-03-25 11:54:24 -04:00
NOTICE Now opening 9.5.3 release. Intent is to formally release 9.5.2 2019-03-21 15:07:39 -07:00
README.md Changed the travis-ci monitoring image to match the current brnach (master). 2018-04-09 21:47:03 -04:00
scheme.1.in Various enhancements and fixes highlighted by profiling performance 2019-09-21 15:37:29 -07:00
workarea Add LZ4 support and use it by default for compressing files 2019-04-06 07:32:37 +02:00

Build Status

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.