I think your initial instinct was right: if you want to change the lexical
structure of your language, the right place to start is in the reader. The
reader is the part of Racket’s language facilities that interprets the
structure of sequences of characters, and your notion of dotted identifiers
It turns out expanding the syntax object isn't the right approach. It seems
easy enough for defining values and simple procedures, but as soon as you
consider optional arguments and keyword arguments, the resulting expansion
gets too complicated to analyze.
I don't see an easy way to do this, u
Is this some expected behavior?
1. Open DrRacket and run:
#lang racket/base
(require pict)
(circle 50)
2. Copy the output. Open a new tab in DrRacket and paste the pict-snip%.
3. This error message showed up at the bottom: ``write: cannot marshal
value that is embedded in compiled code value: (
Is this some expected behavior?
1. Open DrRacket and run:
#lang racket/base
(require pict)
(circle 50)
2. Copy the output. Open a new tab in DrRacket and paste the pict-snip%.
3. An error message showed up at the bottom, similar to this
https://i.imgur.com/5BnTWP0.png
Despite the error message
I cannot help you directly, but I just wanted to say that at my workplace,
we are also behind a proxy, and I did not have to reconfigure Racket in any
way. I also have to put in the "insteadOf" rule for git clones, as only
HTTPS traffic is allowed, but I believe the Racket package manager just
Does anyone have any input on this? This is an important hurdle for my,
hopefully eventual, use of Racket at work, and I imagine it is important to
other industrial users as well.
I have confirmed that it is indeed my work's proxy/firewall that is
blocking Racket's package manager. For now, I h
Thanks Matthew, I think I can adapt that approach. As written, it's not
quite what I had in mind because it disallows foo.bar in an expression
context, before I get a chance to transform it to (bar foo). So I am going
to try to (expand #'(module a racket . EXPRS)) and then search the
fully-expa
> On Dec 9, 2018, at 8:20 PM, default.kra...@gmail.com wrote:
> Is there an easy way to disallow certain characters in identifiers? I
> realized it's not just dots I want to disallow, but also operators like +
> which might be interpreted as infix in certain contexts.
Roughly, I imagine you'd
8 matches
Mail list logo