Discussion:
[racket] Testing modifications to 3rd party packages
Bartosz Przygoda
2015-02-10 14:00:36 UTC
Permalink
Hi,

Suppose I want to test some modification to a package, say: ffi/unsafe. I
fetch racket source code from github, perform modifications (let's just add
*baz* function (and provide it)), fire up a repl (I'm normally using Geiser
for Emacs, but here I will use xrepl):

,en "sources/racket/racket/collects/ffi/unsafe.rkt"

-> baz
#<procedure:baz>

,en #f
,en "sources/test.rkt"
->(require ffi/unsafe)

->baz
; baz undefined

Is it because when I enter such module it's loaded under different path
than when requiring it with short 'ffi/unsafe'? For that matter, I cannot
require it using same path I've used when entering...
Bartosz Przygoda
2015-02-10 14:46:06 UTC
Permalink
Sorry for noise. Indeed it has to be required by the same path as the one
used for entering, but this time it worked.
Post by Bartosz Przygoda
Hi,
Suppose I want to test some modification to a package, say: ffi/unsafe. I
fetch racket source code from github, perform modifications (let's just add
*baz* function (and provide it)), fire up a repl (I'm normally using Geiser
,en "sources/racket/racket/collects/ffi/unsafe.rkt"
-> baz
#<procedure:baz>
,en #f
,en "sources/test.rkt"
->(require ffi/unsafe)
->baz
; baz undefined
Is it because when I enter such module it's loaded under different path
than when requiring it with short 'ffi/unsafe'? For that matter, I cannot
require it using same path I've used when entering...
Loading...