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
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:
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
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
4 matches
Mail list logo