I've always thought that should be possible -- for instance, if someone were to implement some pre-existing language in Racket, it would be nice to be able to say "require this using #lang X" so that it can be parsed and bound correctly. Eg. if you had a Javascript implementation and some functions to massage data between what normal Racket and Javascript-inside-Racket expect, it might be fun to be able to consume some node.js libraries that way. At least for libraries that work within whatever implementation you might have.
On Thu, May 5, 2016 at 6:45 PM, Jack Firth <jackhfi...@gmail.com> wrote: > On Thursday, May 5, 2016 at 5:39:44 PM UTC-7, Matthew Flatt wrote: > > At Thu, 5 May 2016 17:32:20 -0700 (PDT), Jack Firth wrote: > > > Does that evaluate the file as if it were entered in a REPL? > > > > Yes. > > What if I don't want REPL semantics, but I want behavior identical to if > the file began with the appropriate #lang line? Is there some subtle reason > that's not an option? > > -- > 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.
