- mmap errors report request size (for debugging 64-bit errors)
- added a config definition for FLAT_TABLES which is not yet used
(32-bit ikarus will use flat segment and dirty tables while 64-bit
ikarus will use two-level tables)
error (as suggested by Derick Eddington).
- The -h or [-b <bootfile>] options must now come first, so,
the rest of the command-line arguments are not scanned: only the
first one or two. The docs (in ikarus -h) already suggested the
correct invocation arguments, so, this conforms to the previously
documented behavior.
Previously, all output ports were unbuffered.
- the console error port is made unbuffered.
The following program:
(begin
(write-char #\a (current-output-port))
(write-char #\b (current-error-port))
(write-char #\c (current-output-port)))
now prints "bac" when run from the repl, when it used to only
print "ac" (the b just sat in the error port).
changed in order to allow large structures (e.g., libraries,
syntax objects, etc.) to print efficiently. This is done by only
traversing the parts of the structure that will actually be
printed, rather than traversing the whole data structure (which is
what write/display used to do). Pretty-print should be fixed in a
similar manner (TODO).
unhandled causing compile time errors.
- fixed some bootstrapping issues with pointer? (which was moved out
of the (ikarus) library)
- freshened up the bootfiles for both 32- and 64-bit version of
ikarus.
- added a missing save to a callee-save register (%edi)
when entering/reentering to Scheme which caused Ikarus
not to run properly depending on whether or not gcc places
the pcb in %edi or not during Scheme execution.
- updated lab/test-ffi.ss to use the new names for foreign
types, etc.
(ikarus system $foreign).
- changed the names of some of the pointer primitives
- changed the name of the procedure make-ffi to make-callout
- updated examples and libraries to conform with new names
- updated the users guide to provide a complete description of
the (ikarus foreign) library
- updated list of missing R6RS features in the users guide
given file one expression at a time. Most notable difference is
observed when the loaded file captures a conitnuation in one
expression. Re-invoking this continuation should evaluate the
next expression that has not been evaluated yet, and not the
expression following the call/cc.
Abdulaziz Ghuloum