[racket-dev] open untagged files in blank language level?

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Thu Oct 6 14:30:30 EDT 2011

Two hours ago, John Clements wrote:
>> Currently, opening a file that doesn't begin with a #lang line
>> results in a window whose language level is inherited from the
>> buffer that was foremost when the open-file was issued (IIUC).

No, it defaults to whatever language you last chose in the language
level (or in the popup at the bottom of the drracket window), unless
it sees a #lang line at the beginning, in which case it uses the 'use
the language declared in the source' language (but that does not count
as changing that last choice).

> I think this is a mistake. I think that instead, the language
> level should revert to "Use the language defined in the source."

I don't want to default to 'use language in source' because of
students that have chose one of the teaching languages. They should
keep getting that student language over and over and not having to
explicitly keep re-choosing it. Unless I misunderstand the proposal
somehow?

On Thu, Oct 6, 2011 at 1:20 PM, Eli Barzilay <eli at barzilay.org> wrote:
> I'd like to
> see the "use the language defined in the source" become the default
> for all purposes

Until the teaching languages work well in this mode, I oppose this
change. Once they do, I'm all for it.

> -- so at least when you open a file that does have a
> `#lang' line, or when you type it in, the non-"use the language
> defined in the source" languages should make it ask you if you want to
> switch to it (to the "use the language defined in the source"
> language).

When you open a file that begins with #lang DrRacket already just
changes the language level (but nothing detects when you type it).

> If anything, just the name of the "use the language defined in the
> source" language is a very long one, which is unfortunate since it's
> often the one that gets recommended often.

Easy to agree here. :)

Robby


Posted on the dev mailing list.