Re: [racket-dev] REPL crash

2010-11-30 Thread Eli Barzilay
5 hours ago, Dmitry Chestnykh wrote: > The following example from docs (11.9) crashes console REPL (but not > gracket or DrRacket): > > (define-namespace-anchor anchor) > (parameterize ([current-namespace > (namespace-anchor->namespace anchor)]) >(expand > (datum->syn

[racket-dev] REPL crash

2010-11-30 Thread Dmitry Chestnykh
The following example from docs (11.9) crashes console REPL (but not gracket or DrRacket): (define-namespace-anchor anchor) (parameterize ([current-namespace (namespace-anchor->namespace anchor)]) (expand (datum->syntax #f '(delay (+ 1 2) Seg fault (inte

[racket-dev] planet package dependencies (was: Re: code base metrics)

2010-11-30 Thread John Clements
While you're in meta-programmer mode, any interest in automatically computing planet dependencies? I'd *love* to know what packages a planet package depends on. I understand that in the presence of dynamic-require, you can only do so well, but even a first approximation could be incredibly usefu

[racket-dev] Thanks, Carl!

2010-11-30 Thread John Clements
Using (require (for-label (planet clements/rsound))) in my documentation just bit me in the butt really hard, when it turns out that installing a not-most-recent version of my planet package automatically triggers installation of the most-recent version, causing much pain for my students. AAH!

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Neil Van Dyke
Going back to a point I'm sure others have made already... Perhaps you guys have a good sense of how many people would be affected by any incompatibilities in this case? Most people use "open-output-file" and hash tables, so you wanted to migrate all those people gently somehow. A relatively

[racket-dev] A game using scheme !

2010-11-30 Thread Toutsurla TI-84
Hello, I'm a french student, and I'd like to create a game, using scheme : a race for 2 players (computer or real person). What i've got to do is to creat a grid, where there is a start line, a finish line and, between them, a random number of lines... In this grid, we have "walls", as in c

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Eli Barzilay
Three hours ago, Robby Findler wrote: > On Tue, Nov 30, 2010 at 8:04 AM, Eli Barzilay wrote: > > Two hours ago, Robby Findler wrote: > >> On Tue, Nov 30, 2010 at 5:18 AM, Eli Barzilay wrote: > >> > > >> > The problem here is that there is no name to change -- it's the > >> > implicit "coercion" o

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Neil Van Dyke
I don't have any important dependencies on the Web Server right now, but just wanted to add that even small backwards-incompatibilities in PLT/Racket have ruffled feathers of consulting clients of mine in the past. When there are backward-incompats, it's *much* better that they be detected at

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Matthias Felleisen
On Nov 30, 2010, at 9:58 AM, Robby Findler wrote: > That said, massive backwards incompatibility as Jay is proposing seems wrong. + a lot _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Robby Findler
On Tue, Nov 30, 2010 at 8:04 AM, Eli Barzilay wrote: > Two hours ago, Robby Findler wrote: >> On Tue, Nov 30, 2010 at 5:18 AM, Eli Barzilay wrote: >> > >> > The problem here is that there is no name to change -- it's the >> > implicit "coercion" of xexpr values to a response. >> >> Why can't ther

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Matthias Felleisen
On Nov 30, 2010, at 9:01 AM, Eli Barzilay wrote: > (The above errors were all over the old pages for years without being > discovered...) Berkeley would have asked if they are really errors then :-) _ For list-related administrative tasks: ht

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Eli Barzilay
Two hours ago, Robby Findler wrote: > On Tue, Nov 30, 2010 at 5:18 AM, Eli Barzilay wrote: > > > > The problem here is that there is no name to change -- it's the > > implicit "coercion" of xexpr values to a response. > > Why can't there be two libraries, one that coerces and one that > doesn't?

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Eli Barzilay
Two hours ago, Neil Van Dyke wrote: > Eli Barzilay wrote at 11/30/2010 06:36 AM: > > The ones I ran into, at least with xexprs: they rely on lots of > > quasi/quotes etc and it's easy to end up with things like > > "nbsp". > > I make errors of not getting my quotes, backquotes, and commas in > the

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Robby Findler
On Tue, Nov 30, 2010 at 5:18 AM, Eli Barzilay wrote: > Yesterday, Robby Findler wrote: >> This kind of thing has happened many times for other parts of the >> system (the class system is a good example). We have generally tried >> to avoid so much breakage and I think we should here. One technique

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Neil Van Dyke
Eli Barzilay wrote at 11/30/2010 06:36 AM: The ones I ran into, at least with xexprs: they rely on lots of quasi/quotes etc and it's easy to end up with things like "nbsp". I make errors of not getting my quotes, backquotes, and commas in the right place sometimes, but those errors tend to be

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Eli Barzilay
On Saturday, Neil Van Dyke wrote: > > BTW, SXML and xexprs are a big win for Web development. For one > large system in PLT Scheme, the architects have repeatedly mentioned > the productivity benefits of SXML for HTML pages as one of the major > advantages of using Scheme. They also have problem

Re: [racket-dev] Removing Xexpr preference from Web Server

2010-11-30 Thread Eli Barzilay
Yesterday, Robby Findler wrote: > This kind of thing has happened many times for other parts of the > system (the class system is a good example). We have generally tried > to avoid so much breakage and I think we should here. One technique > is to have a new name for the new version (or a new name