Or another hack: put the parameter's value in teh filesystem and use
parameter guards to fish it out of there.
This would be useful only if you consider it temporary tho. :)
Robby
On Wed, Dec 7, 2016 at 2:09 PM, Matthew Flatt wrote:
> At Wed, 7 Dec 2016 12:01:24 -0800 (PST), Dan Liebgold wrote
At Wed, 7 Dec 2016 12:01:24 -0800 (PST), Dan Liebgold wrote:
> On Tuesday, December 6, 2016 at 5:00:47 PM UTC-8, Robby Findler wrote:
> >
> > Perhaps there is another way to achieve the effect you want in a way
> > that is more friendly to creating .zo files?
> >
>
> Yes, this is the crux of the
On Tuesday, December 6, 2016 at 5:00:47 PM UTC-8, Robby Findler wrote:
>
> Perhaps there is another way to achieve the effect you want in a way
> that is more friendly to creating .zo files?
>
Yes, this is the crux of the issue. In my case I have a system that deals with
modules that may or may
Thank you, Spencer and Matthew both. That gives me enough to go on with.
On Wed, Dec 7, 2016 at 9:59 AM, Matthew Flatt wrote:
> Maybe there's some technical reason that I've forgotten, but I think
> it's just that `hash` is newer and was an experiment toward a better
> interface. A `mutable-ha
Maybe there's some technical reason that I've forgotten, but I think
it's just that `hash` is newer and was an experiment toward a better
interface. A `mutable-hash` function would make sense, as far as I can
tell.
Meanwhile, something like `(hash-copy (hash 'a 1 'b 2))` might be the
most convenie
For symmetry there is "make-immutable-hash", which is like "hash" but has
the interface of "make-hash". (I don't know why "hash" is the way it is
though).
--spencer
On Wed, Dec 7, 2016 at 10:49 AM David Storrs wrote:
> -> (hash 'a 1 'b 2)
> '#hash((a . 1) (b . 2))
>
> -> (make-hash '((a . 1) (b
-> (hash 'a 1 'b 2)
'#hash((a . 1) (b . 2))
-> (make-hash '((a . 1) (b . 2)))
'#hash((b . 2) (a . 1))
-> (make-hash 'a 1 'b 2)
(make-hash 'a 1 'b 2)
; make-hash: arity mismatch;
; the expected number of arguments does not match the given number
; expected: 0 to 1
; given: 4
; [,bt for contex
My initial reaction would be to explicitly split “module.rkt” into two pieces:
— its compile-time code especially an exported parameter a
— its run-time code, which uses the same parameter
Your client module could then require each piece at the correct phase.
This also ought to work with the
8 matches
Mail list logo
