Re: [racket-users] unclear about this `parameterize` behavior

2015-08-30 Thread Alexander D. Knauth
To add to that a little bit, this is what I found: #lang multi-file #file param.rkt #lang racket (provide my-param) (define my-param (make-parameter 'default)) #file param-test.rkt #lang racket (require "param.rkt") (define-namespace-anchor a) (parameterize ([current-namespace (make-base-namespace

Re: [racket-users] unclear about this `parameterize` behavior

2015-08-30 Thread Matthew Flatt
The `make-base-namespace` function creates a new namespace, but it attaches the `racket/base` instance of the current namespace to the new one. The `error-print-width` parameter comes from `racket/base`, so it's still the same parameter. You can use `namespace-attach-module` to attach "param.rkt"

[racket-users] unclear about this `parameterize` behavior

2015-08-30 Thread Matthew Butterick
In the example below, I'm curious about the reason for the difference between the behavior of the system parameter `error-print-width` and the custom parameter `my-param`. I understand why `my-param` doesn't take the parameterized value 'custom (= because `namespace-require` causes a fresh ins