[Slib-discuss] Writing *.init-File

[address@hidden]

I have tried it : I needed to do some modification (e.g. my Scheme does
not offer "rational?") After fitting myscheme.init and loading it I get:

> Loading "/data/brblo/Tools/Scheme/slib/myscheme.init"
Loading "/usr/share/slib/require.scm"

Error: eval: unbound variable
Error Object: env

How can I find out where this error comes from? Thanks.

Regards

Bastian

Am 26.03.2010 02:44, schrieb Aubrey Jaffer:
>  | Date: Thu, 25 Mar 2010 22:17:28 +0100
>  | From: "address@hidden" <address@hidden>
>  | 
>  | Dear group,
>  | 
>  | I try to write a new *.init file for a Scheme-Interpreter not yet
>  | included in slib.  Is there some documentation how to do this?
>  | Every help is welcome.  Thanks.
>
> Look at Template.scm and *.init for examples.  The documentation is at
> <http://people.csail.mit.edu/jaffer/slib_8.html#SEC281>
>
>   Porting
>
>   If there is no initialization file for your Scheme implementation,
>   you will have to create one.  Your Scheme implementation must be
>   largely compliant with
>   IEEE Std 1178-1990,
>   Revised^4 Report on the Algorithmic Language Scheme, or
>   Revised^5 Report on the Algorithmic Language Scheme
>   in order to support SLIB. (8)
>
>   http://cvs.savannah.gnu.org/viewcvs/*checkout*/scm/scm/r4rstest.scm
>   is a file which checks compliance with much of R4RS.
>
>   `Template.scm' is an example configuration file.  The comments
>   inside will direct you on how to customize it to reflect your
>   system.  Give your new initialization file the implementation's name
>   with `.init' appended.  For instance, if you were porting foo-scheme
>   then the initialization file might be called `foo.init'.
>
>   Your customized version should then be loaded as part of your scheme
>   implementation's initialization.  It will load `require.scm' from
>   the library; this will allow the use of provide, provided?, and
>   require along with the vicinity functions (these functions are
>   documented in the sections section Feature and section Require).
>   The rest of the library will then be accessible in a system
>   independent fashion.
>
>   Please mail new working configuration files to agj @ alum.mit.edu so
>   that they can be included in the SLIB distribution.
>
>