Ooh, thank you Oak and Jens Axel! I would never have figured that out.
As Matthew's email from Jan 2020 says, having the documentation say
something (and, in particular, suggesting the use of `parameterize` to get
what many users might expect) would be quite lovely.
(Thanks also, Greg.)
Shriram
Den tir. 21. jul. 2020 kl. 20.25 skrev Sorawee Porncharoenwase <
sorawee.pw...@gmail.com>:
> This is weird. I usually parameterize current-namespace when using
> namespace-* functions, and in this particular case it works fine.
>
> On Tue, Jul 21, 2020 at 11:05 AM Shriram Krishnamurthi
> wrote:
>
This is weird. I usually parameterize current-namespace when using
namespace-* functions, and in this particular case it works fine.
On Tue, Jul 21, 2020 at 11:05 AM Shriram Krishnamurthi
wrote:
> Thank you! Would you know why I might get this error:
>
> ; require: unknown module
>
> ; module
Thank you! Would you know why I might get this error:
; require: unknown module
; module name:
; #>
(This is from inside a module.)
Trying the same at the REPL, I see the same thing:
> (define n (make-base-namespace))
> (namespace-require `(file ,(path->string (build-path "wheats" "w1.
Den tir. 21. jul. 2020 kl. 17.45 skrev Shriram Krishnamurthi <
shri...@gmail.com>:
> How I can combine these three? I want to do something like this:
>
> (define n (make-base-namespace))
> (define p (build-path f))
> (eval `(require ,p) n)
>
> Racket doesn't like that: bad syntax for r
How I can combine these three? I want to do something like this:
(define n (make-base-namespace))
(define p (build-path f))
(eval `(require ,p) n)
Racket doesn't like that: bad syntax for require sub-form because p is a
path-typed value.
Essentially, I want to inject the module at f
6 matches
Mail list logo
