Because it was changed to be based on "#lang racket" instead of the (old) "#lang mzscheme" not too long ago. I think there was a post here (or on the users's list) about this, but I'm not sure that this particular point was mentioned there, so I can see how you'd be surprised.
Is this causing you trouble with classes or similar? Would a "#lang eopl/mzscheme" or something like that be useful for backwards compatibility? (You'd still need to use that #lang line, tho, since the regular eopl language is now changed for good.) Robby On Mon, Apr 2, 2012 at 7:09 PM, Nadeem Abdul Hamid <nad...@acm.org> wrote: > How come when building Racket from the latest source of the repository > (at least as of 3 days ago), #lang eopl doesn't recognize > (all-defined) as a valid provide spec and wants (all-defined-out) > instead? > --- nadeem > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev _________________________ Racket Developers list: http://lists.racket-lang.org/dev
