Using EOPL3 Code in Racket

[Todd Neller]

What is the current recommended way of using EOPL3 text code with
Racket?

My best understanding is that one specifies "#lang eopl" on the first
line of source files, but I don't seem to be correctly importing
definitions using "require" on files included in allfiles.zip from the
text.

Could someone provide a simple example of how one would typically
specify both language and module usage for student EOPL3 code?

Thanks,
Todd

[Mitchell Wand]

Dear Todd,

Sorry about the delay in answering your question--

The short answer is that code from the archive seems to run just fine, as is, in Racket 5.1.3 .

A slightly longer answer:  Remove the

(module name (lib "eopl.ss" "eopl") ....  )

wrapper, and write #lang eopl at the top of the file instead.  

If you are feeling more adventurous, you can try to adapt the code base to use the rackunit testing framework instead of the kludgy one I threw together for the book.  I have somebody working on a longer document describing this, which I'm hoping to post soon.

Again, apologies for the delay.

--Mitch

--
You received this message because you are subscribed to the Google Groups "EOPL3" group.
To post to this group, send email to eo...@googlegroups.com.
To unsubscribe from this group, send email to eopl3+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/eopl3?hl=en.

[Mitchell Wand]

Update:

If the module says (module name mzscheme ...), say #lang mzscheme instead.  (Don't say #lang racket -- the syntax for require/provide is slightly different).

I've now also posted this information at www.eopl3.com/code.html .

--Mitch