I learned about identifier macros mostly from scrambling through the
racket sources. There they are often seen in places where macros are used
instead of functions to avoid the cost of a function call. Normally.
macros have the drawback that they can't be passed around or applied like
I'd like to improve the documentation, but I can't tell which part
you're talking about. (The only place where I can find identifier
macros is in the Guide, but that's about `syntax-rules' versus
`syntax-id-rules'.) Can you point to the part that you're reading and
the specific text that seems
I think two additions/refinements would be good here:
1. The section on identifier macros in the Guide (16.1.5) should mention that
define-syntax introduces short-hands for identifiers, period. That is, the
following interaction works perfectly fine:
(define-syntax (foo stx) #'7)
(+ foo
At Wed, 5 Dec 2012 09:41:37 -0500, Matthias Felleisen wrote:
I think two additions/refinements would be good here:
1. The section on identifier macros in the Guide (16.1.5) should mention that
define-syntax introduces short-hands for identifiers, period.
I think a `define-syntax' that
On looking back, my confusion was not entirely due to the documentation,
but partly from my own expectations coming in to it. If I just look up
identifier macro, trying to figure out how to write one, I get a link to
section 16.1.5. This does not directly state the context involving
At Wed, 5 Dec 2012 14:25:29 -0500, Carl Eastlund wrote:
On looking back, my confusion was not entirely due to the documentation,
but partly from my own expectations coming in to it. If I just look up
identifier macro, trying to figure out how to write one, I get a link to
section 16.1.5.
Actually I would hope that section 1.2 (syntax model) in the reference would
explain exactly how macros are invoked. Unless I'm missing something it never
mentions exactly what syntax object is passed to the transformer function once
a macro binding is observed.
It could either go in paragraph
On Tue, Dec 4, 2012 at 3:56 PM, Matthew Flatt mfl...@cs.utah.edu wrote:
I'm not sure...
Providing error-code information is an appealing idea. Instead of
`exn:fail:errno', we'd probably add a `prop:exn:error-code' property
that is implemented by subtypes of `exn:fail:filesystem', etc. Also,
Hi,
I've just created the pull request 186 (https://github.com/plt/racket/pull/186)
which fixes a bug with the language configuration dialog.
As I have disabled a bunch of languages for which I have no use, the language
configuration dialog is not showing anymore.
My patch only fixes the issue
That would be great!
And your commit also seems good to me.
I tried to push it to our repo but somehow I can't see to actually get
things locally into the right state so if someone else has time to do that,
I would much appreciate it.
Robby
On Wednesday, December 5, 2012, Philippe Mechaï
I've now pushed this.
Sam
On Wed, Dec 5, 2012 at 5:02 PM, Robby Findler
ro...@eecs.northwestern.edu wrote:
That would be great!
And your commit also seems good to me.
I tried to push it to our repo but somehow I can't see to actually get
things locally into the right state so if someone
On Sun, Dec 2, 2012 at 11:11 AM, Matthew Flatt mfl...@cs.utah.edu wrote:
At Sun, 2 Dec 2012 10:55:01 -0500, Sam Tobin-Hochstadt wrote:
I have mostly the opposite impression of `raco link`. I like the
default behavior, but that may be a result of my use of a set of
scripts [1] for managing
Thanks!
On Wed, Dec 5, 2012 at 5:53 PM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote:
I've now pushed this.
Sam
On Wed, Dec 5, 2012 at 5:02 PM, Robby Findler
ro...@eecs.northwestern.edu wrote:
That would be great!
And your commit also seems good to me.
I tried to push it to our repo but
I submitted a pull request at [https://github.com/plt/racket/pull/184]
to fix a bug in the implementation of prop:cpointer. Using a procedure
value for that property doesn't currently work. My tiny patch fixes
that.
-Jon
_
Racket Developers list:
Given that context, maybe the right thing here is (a)
installation-specific packages by default and (b) a way to *upgrade*
an existing installation when installing. That might be as simple as
automatically running 'raco pkg migrate', but I think making it part
of the installation step would
15 matches
Mail list logo
