Benjamin Slade writes: > When run Racket, in the REPL, the first command I execute runs fine. But > the second (no matter what it is, even if it's just the first again) > always produces: > > ; ptr-ref: contract violation > ; expected: (and/c cpointer? (not/c (lambda (p) (pointer-equal? p #f)))) > ; given: #f > ; argument position: 1st > ; [,bt for context] > ; ptr-ref: contract violation > ; expected: (and/c cpointer? (not/c (lambda (p) (pointer-equal? p #f)))) > ; given: #f > ; argument position: 1st > ; [,bt for context] > > And it doesn't accept any more input after that point (including ",bt").
Huh... I'm getting this too. I hadn't noticed it because I use racket-mode for all my REPL hacking, where it isn't appearing (probably because racket-mode has its own REPL protocol code).
