[racket-dev] #f instead of path-string? when (require cKanren)

2014-10-04 Thread A.J. Lepper
Windows 64-bit, Racket v6.1 64-bit If I install cKanren from the package manager then (require cKanren) works fine in Racket.exe from the command prompt, but produces an error in DrRacket. simple-form-path receives #f instead of a path-string?, from file-stamp-in-paths. Adding a [(false? (car

Re: [racket-dev] #f instead of path-string? when (require cKanren)

2014-10-04 Thread Matthias Felleisen
Could you use the github issue tracker to submit this? Thanks -- Matthias https://github.com/calvis/cKanren On Oct 2, 2014, at 12:05 PM, A.J. Lepper wrote: Windows 64-bit, Racket v6.1 64-bit If I install cKanren from the package manager then (require cKanren) works fine in Racket.exe

Re: [racket-dev] #f instead of path-string? when (require cKanren)

2014-10-04 Thread Robby Findler
Do we have a github issue tracker for drracket? Robby On Sat, Oct 4, 2014 at 5:48 PM, Matthias Felleisen matth...@ccs.neu.edu wrote: Could you use the github issue tracker to submit this? Thanks -- Matthias https://github.com/calvis/cKanren On Oct 2, 2014, at 12:05 PM, A.J. Lepper wrote:

Re: [racket-dev] #f instead of path-string? when (require cKanren)

2014-10-04 Thread Robby Findler
I'm not able to reproduce this bug, but it appears that the value of the current-load/use-compiled parameter is being passed #f for a first argument. The code in DrRacket seems to assume that things like this will raise errors: (parameterize ([current-load/use-compiled void])