Re: [racket-users] upcoming v6.2.1

2015-08-03 Thread Ryan Davis
> > On Jul 29, 2015, at 08:16, Matthew Flatt wrote: > > We're preparing a v6.2.1 release, which will go out before August 10. > The v6.2.1 build will be a small set of patches to v6.2, i.e., not > derived from the current development branch. > > The patches are for the HtDP teaching languages.

Re: [racket-users] Macro that does substitution

2015-08-03 Thread Matthias Felleisen
Correct. There should never be an exception because the value never ends up in a strict position. -- Matthias On Aug 3, 2015, at 12:44 PM, Andrew Gwozdziewycz wrote: > On Wed, Jul 29, 2015 at 9:30 AM, Matthias Felleisen > wrote: > > On Jul 29, 2015, at 7:50 AM, Klaus Ostermann wrote: >

Re: [racket-users] Macro that does substitution

2015-08-03 Thread Andrew Gwozdziewycz
On Wed, Jul 29, 2015 at 9:30 AM, Matthias Felleisen wrote: > > On Jul 29, 2015, at 7:50 AM, Klaus Ostermann wrote: > > > Thanks, Matthew and Matthias. The service on this mailing list is > incredible! > > > > I know it is not cbn because it is local, but a better name didn't come > to my mind and

[racket-users] Re: postgresql-connect and #:notification-handler

2015-08-03 Thread Tim Brown
I've just noticed that Ryan Culpepper pushed: https://github.com/racket/db/commit/e6b28703c5f04084565deb2aee34691ccc9b35fa to the database library; titled: “add async-message-evt method to postgresql connections” Thanks Ryan. Tim On Tuesday, July 14, 2015 at 3:21:16 PM UTC+1, Tim Brown wrote: >

Re: [racket-users] continuing after a user break

2015-08-03 Thread Robby Findler
It does seem useful. It would require some thought because the exception handler cannot escape until there is no possibility of resuming which seems like it would have UI implications. This would also cause some REPL interactions to behave differently when they are in the break-resumable context (n

Re: [racket-users] eval PSA (was Sending Closures to Places)

2015-08-03 Thread Jens Axel Søgaard
On eval in dynamic languages generally and in Racket specifically Posted by Matthew Flatt http://blog.racket-lang.org/2011/10/on-eval-in-dynamic-languages-generally.html 2015-08-03 13:32 GMT+02:00 Josh Grams : > O

Re: [racket-users] eval PSA (was Sending Closures to Places)

2015-08-03 Thread Josh Grams
On 2015-08-03 01:22AM, Neil Van Dyke wrote: > Eval might indeed be the perfect solution this time, iff every other > conceivable alternative has been rejected. :) > > Shameless link to PSA on the topic of eval: > http://lists.racket-lang.org/users/archive/2014-July/063597.html > > Suggestions f

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 : > 2015-08-02 19:12 GMT+02:00 Konstantin Weitz : > >> I'm trying to

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 : > 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 `pl

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 alt

Re: [racket-users] Optimizing closures

2015-08-03 Thread Laurent
I see, thanks for the explanations, Matthew. So that's the kind of things that are "simple in principle, but more complicated than one would like in practice" then. Good luck with your experiments! On Fri, Jul 31, 2015 at 10:02 PM, Matthew Flatt wrote: > At Fri, 31 Jul 2015 18:56:15 +0100, Laure