Re: [racket-dev] provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

2012-04-05 Thread David Van Horn
On 4/2/12 8:42 PM, Nadeem Abdul Hamid wrote: OK, thanks. Just wanted to make sure something wasn't broken. It's only a minor inconvenience - my students are using the version from the download page, while I usually use one built from source, but I've just been using the regular 5.2.1 version to

[racket-dev] provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

2012-04-02 Thread Nadeem Abdul Hamid
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:

Re: [racket-dev] provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

2012-04-02 Thread Robby Findler
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

Re: [racket-dev] provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

2012-04-02 Thread Nadeem Abdul Hamid
OK, thanks. Just wanted to make sure something wasn't broken. It's only a minor inconvenience - my students are using the version from the download page, while I usually use one built from source, but I've just been using the regular 5.2.1 version to run their programs. In any event, perhaps the