+1

Yes, specifying the language to use when interpreting some source, is best in 
the input source itself than in the reference to that source.

But why must it be one or the other, and not some sensible combination of both. 
e.g. If the #lang is absent from the source, look for and/or override the 
language to use with command line switches to the interpreter, with #lang 
racket (or racket/base or something else) as the default.

The only way Racket-created solutions can supplant the products created with 
medieval tools (and I'm thinking here of lex, yacc, and their ilk) is by 
ingesting the exact same input source files/streams that those other products 
ingest. Forcing a change to input source is an unnecessary, difficult, and 
often insurmountable hurdle. Evolving replacement Racket-built solutions in 
(one of the many) domains where Racket is ideal should be easy.

> On May 7, 2016, at 6:48 AM, Jay McCarthy <jay.mccar...@gmail.com> wrote:
> 
> +1
> 
>> On Fri, May 6, 2016 at 6:13 PM, Jack Firth <jackhfi...@gmail.com> wrote:
>> William's remark is spot on about my use-case. There exists a language that 
>> wasn't initially designed with racket in mind, but could easily be a racket 
>> #lang. To interop with code already written in this language, I wanted an 
>> easy way to run files that don't have the #lang line. If I were designing 
>> the language Racket-first, I wouldn't need this feature.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> -- 
> Jay McCarthy
> Associate Professor
> PLT @ CS @ UMass Lowell
> http://jeapostrophe.github.io
> 
>           "Wherefore, be not weary in well-doing,
>      for ye are laying the foundation of a great work.
> And out of small things proceedeth that which is great."
>                          - D&C 64:33
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to