I'm not sure exactly why my syntax class wasn't working, but it is working
now. I had an extra set of parentheses around the ~between pattern, so it
may have been related to that. Whatever the case may be, the non-splicing
syntax class is working now.
I am very close to getting everything worki
I believe your two syntax classes are identical, except for the fact that the
splicing variant will not be allowed as a single term pattern. Therefore, I
don’t think there’s ever any reason to prefer the splicing version.
I tried an example using your mag-lvl syntax class with ~between, and it w
You're overgeneralising. Po-files support more things than string constants
format however that is not important in the context of translating Racket.
You can convert string constants to po, translate and then convert back.
Comments can become translator comments.
Pointers can be modelled with mshs
Regarding my custom syntax-class issue, I realize now that it is probably
because ~between only accepts splicing syntax classes. So, I created one
that matches my regular syntax class. I'm not 100 percent sure that these
are interchangeable in my use case though:
(define-syntax-class mag-lvl
:wave: Hi all, Josh pointed me to this thread. I'm the author of that blog post
he linked to.
Sam Tobin-Hochstadt wrote:
> The Racket community, and even more so the design of Racket
> concurrency APIs, is very strongly influenced by the academic side of
> Racket. As far as I can tell, structured
5 matches
Mail list logo
