Re: [racket-users] Connecting a language and its reader

2017-10-03 Thread Matthew Butterick
> On Oct 1, 2017, at 12:50 PM, Jordan Johnson wrote: > > Correct me if I’m wrong in this understanding: the #'(module ...) is > effectively replacing the body of whatever program is written in #lang > mylang, so the path-string "semantics.rkt" must be interpreted relative to > that program’s

Re: [racket-users] Connecting a language and its reader

2017-10-01 Thread Jordan Johnson
Ok. Thanks, Philip! —jmj > On Oct 1, 2017, at 5:04 PM, Philip McGrath wrote: > > Using `mylang/semantics` will work as long as you have the `mylang` > collection installed, which is necessary for `#lang` to work anyway. > > In cases when it is sensible to use your new language without the cust

Re: [racket-users] Connecting a language and its reader

2017-10-01 Thread Philip McGrath
Using `mylang/semantics` will work as long as you have the `mylang` collection installed, which is necessary for `#lang` to work anyway. In cases when it is sensible to use your new language without the custom reader (e.g. for languages which don't have a custom reader), it is often pleasant to ha

[racket-users] Connecting a language and its reader

2017-10-01 Thread Jordan Johnson
Hi all, I’ve been putting together a little language to learn more about how the Racket #lang ecosystem works, and I’m hung up on bundling up the language as a collection. I’m not sure I correctly understand the point where the reader attaches to the macros that specify how to expand the langua