On Wed, Aug 10, 2016 at 8:10 AM, Alex Knauth <alexan...@knauth.org> wrote: >> I believe this fixes a bug in DrRacket but the way these handlers are >> set up is pretty complicated. Here's an example program that behaves >> differently in 6.6 and the version with those commits. I think the 6.6 >> behavior is wrong (i.e. the newlines between the three numbers should >> be appearing). My inference is based on a reading of the docs and some >> experimentation with the racket binary. In particular, the docs say >> that `print` should be printing a newline, and they say that `print` >> should be calling the global-port-print-handler. Thus, even when the >> global-port-print-handler doesn't print a newline we should still see >> one. > > When I read the docs to see what `#lang constructor-style-print` should do, it > said two things. One, that `current-print` should print a newline. Two, that > `global-port-print-handler` and `print` should do the same thing, which is > *not* print a newline, because `print` doesn't print one (that's `println`'s > job).
Sorry: I wrote print but meant current-print. Regardless, DrRacket's current behavior seems to be in line with the racket binary and the documentation. Robby -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
