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
I have no explanation, but I can get a longer version of the error message.
If you change the definitions to:
#lang racket
(new object%)
(define-namespace-anchor nsa)
(define ns (namespace-anchor->namespace nsa))
And then evaluate at the REPL:
> (eval '(new object%) ns)
You get this error mes
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
Here's a workflow that is working well for me, now that things have settled.
In a Racket window, I have my package foo's scribble source file open:
/Users/username/github/foo/scribblings/foo.scrbl
I have the Package Manager open, and I keep it open, with the checkbox
checked "Updates can repla
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
Hi,
Does anyone know a good explanation as to why the following code works
depending on whether the apparently-useless line is commented out?
#lang racket
#;(new object%) ; uncommenting this raises an error
(define-namespace-anchor nsa)
(define ns (namespace-anchor->namespace nsa))
(eval '(new
6 matches
Mail list logo