In v5.3.0.24, the new `current-compiled-file-roots' parameter and
associated PLTCOMPILEDROOTS environment variable give you more control
over where bytecode files are written.
The new parameter holds a list of paths. When looking for a compiled
file, the default `load/use-compiled' handler checks
It doesn't seem to matter how I set up the evaluator (using
`make-base-eval' or `make-evaluator'). If an example fails to typecheck,
it looks like an ugly documentation error. This is an actual example in
the math docs, which I would really like to keep:
> (flabs (exact->inexact 0.5f0))
eval:8
2 matches
Mail list logo