[racket] Places acting differently in DrRacket and Racket

The whole enclosing module (file) is executed again on every call to place.
Add a print before the place start to see it. Seems to be broken since <  
5.2.1.

On Thu, 18 Oct 2012 06:39:56 +0200, Nick Shelley <nickmshelley at gmail.com>  
wrote:

> It looks like that was the problem. Thanks!
>
> However, if I add (place-wait p) after defining p as the place, DrRacket
> runs out of memory (and never prints anything), while Racket gives a
> "place: scheduler pipe failed" error and runs the place body about 50
> times. Anything else obvious I'm missing?
>
> On Wed, Oct 17, 2012 at 10:26 PM, Robby Findler  
> <robby at eecs.northwestern.edu
>> wrote:
>
>> Does your racket program exit before the place runs?
>>
>> Robby
>>
>> On Wed, Oct 17, 2012 at 11:12 PM, Nick Shelley <nickmshelley at gmail.com>
>> wrote:
>> > It's usually the case that I'm just missing something obvious, but  
>> when I
>> > have a file that just creates a place that prints something and I run  
>> it
>> in
>> > DrRacket, I see the thing printed after a slight pause, but when I run
>> the
>> > file with the racket executable from the command line, I don't see
>> anything.
>> > Just to make sure it wasn't some output-port difference, I also had  
>> this
>> > code:
>> >
>> > (require racket/place)
>> > (define p (place x (system "touch /tmp/file")))
>> >
>> > and sure enough, when run from DrRacket that file gets created, but  
>> not
>> when
>> > run from the command line.
>> >
>> > Can someone explain what I'm missing?
>> >
>> > ____________________
>> >   Racket Users list:
>> >   http://lists.racket-lang.org/users
>> >