On Feb 9, 2016, at 7:53 PM, Matthew Flatt wrote:
> I think the main issue is that `htdp/bsl/runtime` changed the way it
> configures the printer. Instead of setting `current-print`, it sets
> `global-port-print-handler`. Meanwhile, `interaction` prints within the
> sandbox only if `current-print
Thank you so much. This works like a charm!
Suzanne
> On Feb 9, 2016, at 7:53 PM, Matthew Flatt wrote:
>
> I think the main issue is that `htdp/bsl/runtime` changed the way it
> configures the printer. Instead of setting `current-print`, it sets
> `global-port-print-handler`. Meanwhile, `intera
I think the main issue is that `htdp/bsl/runtime` changed the way it
configures the printer. Instead of setting `current-print`, it sets
`global-port-print-handler`. Meanwhile, `interaction` prints within the
sandbox only if `current-print` is changed from its default value,
which is `pretty-print-
Prior to v6.3, I was able to create a BSL evaluator with the following set up:
@(define-syntax-rule
(*sl-eval module-lang reader def ...)
;; ===>>>
(let ()
(define me (make-base-eval))
4 matches
Mail list logo