A few minutes ago, Scott Klarenbach wrote:
> Thanks Eli. Since I can say #lang at-exp racket/base,
(That's because it extends the `racket/base' reader.)
> I assumed that if "my-lang.rkt" exports all of racket-base that it
> would work. But I suppose that is because racket/base acts as a
> modu
Thanks Eli. Since I can say #lang at-exp racket/base, I assumed that if
"my-lang.rkt" exports all of racket-base that it would work. But I suppose
that is because racket/base acts as a module language and a reader, and
that when I export it from my module language I'm missing the key
ingredient?
Yesterday, Scott Klarenbach wrote:
>
> I assumed that #lang at-exp "my-lang.rkt" should work, since I'm
> wanting to use at-exp syntax with "my-lang.rkt" semantics. I'll
> keep digging and I'm sure it will click.
The way to think about it is that the `at-exp' language adds at
expressions to some
Thanks Matthew. That worked, but I don't fully understand why. Is having
2 reader langs before the 3rd module lang unique to s-exp here, or is it
possible to chain multiple custom reader languages together like you've
done?
I assumed that #lang at-exp "my-lang.rkt" should work, since I'm wanting
You're right that `at-exp` isn't like `s-exp`, but you can use
#lang at-exp s-exp "my-lang.rkt"
At Thu, 9 Jan 2014 18:00:44 -0800, Scott Klarenbach wrote:
> I have a file that starts with:
>
> #lang at-exp racket/base
>
> I then have a bunch of require and init boilerplate that I'd like to mo
5 matches
Mail list logo
