[racket-users] DrRacket fights `racket` on print behavior in `#lang racket/base`

2015-11-27 Thread Paolo Giarrusso
Here's an example showing that this test will not behave consistently in DrRacket and Racket, because `print` won't. Is that a bug, or is it a "bad practice (tm)" that I ever use `print` programmatically and expect specific output? Take the question as "me learning Racket, somewhat

Re: [racket-users] DrRacket fights `racket` on print behavior in `#lang racket/base`

2015-11-27 Thread George Neuner
It's definitely due to printing the values. Notice that it also happens in DrRacket when "show sharing in values" is selected on the Choose Language dialog. I'm not aware of a way to prevent the reader from creating objects with shared structure. You can explicitly disallow use of the #0=