Re: [racket-users] Sending Closures to Places

2015-08-03 Thread Michael Titke
On 03/08/2015 07:22, Neil Van Dyke wrote: Michael Titke wrote on 08/03/2015 12:50 AM: Perhaps /quote/ and /eval/ would do the job? That is the usual way to treat Scheme code as data and data as Scheme code. Eval might indeed be the perfect solution this time, iff every other conceivable

Re: [racket-users] Sending Closures to Places

2015-08-03 Thread Jens Axel Søgaard
2015-08-02 19:12 GMT+02:00 Konstantin Weitz konstantin.we...@gmail.com: I'm trying to write a distributed racket program using [places][0]. From my current understanding, this means that I have to send data to each place over a channel using the `place-channel-put` function, which can send any

Re: [racket-users] Sending Closures to Places

2015-08-03 Thread Jens Axel Søgaard
Note that the web-server has support for serializable closures: http://docs.racket-lang.org/web-server-internal/closure.html I think they are the practical choice. /Jens Axel 2015-08-03 12:29 GMT+02:00 Jens Axel Søgaard jensa...@soegaard.net: 2015-08-02 19:12 GMT+02:00 Konstantin Weitz

Re: [racket-users] Sending Closures to Places

2015-08-02 Thread Michael Titke
On 02/08/2015 19:12, Konstantin Weitz wrote: I'm trying to write a distributed racket program using [places][0]. From my current understanding, this means that I have to send data to each place over a channel using the `place-channel-put` function, which can send any value accepted by

[racket-users] Sending Closures to Places

2015-08-02 Thread Konstantin Weitz
I'm trying to write a distributed racket program using [places][0]. From my current understanding, this means that I have to send data to each place over a channel using the `place-channel-put` function, which can send any value accepted by `place-message-allowed?`. I would like to send

Re: [racket-users] Sending Closures to Places

2015-08-02 Thread Neil Van Dyke
Michael Titke wrote on 08/03/2015 12:50 AM: Perhaps /quote/ and /eval/ would do the job? That is the usual way to treat Scheme code as data and data as Scheme code. Eval might indeed be the perfect solution this time, iff every other conceivable alternative has been rejected. :) Shameless