[plt-dev] `rico' and ".rkt"

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Mon Feb 15 13:27:30 EST 2010

On Mon, Feb 15, 2010 at 12:20 PM, Neil Van Dyke <neil at neilvandyke.org> wrote:
> Robby Findler wrote at 02/15/2010 12:52 PM:
> On Mon, Feb 15, 2010 at 11:38 AM, Neil Van Dyke <neil at neilvandyke.org>
> wrote:
> Would it work to make the automagical translation happen *only* if ".ss" is
> specified (which is what all the legacy code has)?  Then, if ".rkt" or no
> extension is specified, then assume the filename has ".rkt", and never
> assume ".ss".
> There may be legacy code providers, too. Ie a planet package that has
> a "main.ss" file intead of a "main.tekcar" (or whatever the extension
> ends up being).
> I'd say that people would continue to say "main.ss" in this case.  Then, the
> automagical rule for ".ss" in references will keep their code running if
> that package ever renames the file to "main.rkt".
> Basically, seeing ".ss" in code is a sign that legacy code is involved one
> one or both ends, so that's when the automagical backward-compatible stuff
> kicks in.
> When code instead says ".rkt" or (my proposal) has no extension at all then
> we know legacy code is *not* on either end, so we don't pollute the behavior
> of new code with the backward-compatibility kludge.

But main.ss is what you currently get if you don't specify a file at
all, and you can write (planet plai/plai:1/mutator) to get the
"mutator.ss" file.


Posted on the dev mailing list.