Re: [racket] link: module mismatch

2012-11-29 Thread Matthew Flatt
I think it's some mismatch in the way that scheme_eval() uses its namespace argument versus using `(current-namespace)', while `eval' sets `current-namespace'. In other words, scheme_eval() is probably broken in some way when the namespace you give it is not the same as `(current-namespace)'. At

Re: [racket] link: module mismatch

2012-11-28 Thread Anthony Carrico
On 11/29/2012 01:20 AM, Anthony Carrico wrote: > (module+ test > (check = 4 (scheme_eval '(+ 2 2) (make-base-namespace > Hmm, a clue, this doesn't fail: (module+ test (check-false (scheme_eval '#f (make-base-namespace -- Anthony Carrico signature.asc Description: OpenPGP digital

[racket] link: module mismatch

2012-11-28 Thread Anthony Carrico
I have a test case that works at the command line: $ racket Welcome to Racket v5.3.1. > (require "simple.rkt") > (scheme_eval '(+ 2 2) (make-base-namespace)) 4 > But fails with raco test: $ raco test "simple.rkt" link: module mismatch; possibly, bytecode file needs re-compile because dependenci