DrRacket: #lang eopl vs the language dialog

[Robby Findler]

Hi folks: I'm wondering if it now time to drop support for the
language-dialog incarnation of EOPL in DrRacket, in favor of the
"#lang eopl" variant. Any opinions?

Thanks,
Robby

[Robby Findler]

Okay, so it sounds like no one minds.

I've made this change in the pre-release version of DrRacket. Please
let me know if anyone spots any problems.

Thanks,
Robby

> --
> 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.
>
>

[Brian Lavender]

Uh, I was working through the EOPL book and while not a lot of people
are using it at the present, I think it is valuable. I would like to
vote for having the support available. I worked through the example
code for maintaining state in different environments and I thought it
was especially valuable, yet I need to spend time to continue with it.

brian

[Brian Lavender]

Darn it. I should read more closely. I see that you are proposing
support for a language-dialog? Hmm, ok.

It has been a while since I used the #lang eopl. What is it that it
does exactly? (Insert foot in mouth now)

brian

[Robby Findler]

Your programs should all continue to work in DrRacket. Instead of
opening the language dialog and selecting "EoPL" you should open it
and choose "Use the language declared in the source" and then start
your file with this line:

#lang eopl

(with no initial spaces preferably).

Generally speaking #lang-style language specifications are preferred
in the Racket world as the tools we have work better when each file is
explicit about the language it is written in. (I was motivated to
remove the support I removed by one such missing piece of
functionality in fact.)

Hopefully that clarifies.

Robby