[racket-dev] safe version of racket/unsafe/ops?

2010-09-27 Thread John Clements
I'm sure I'm just missing something obvious here, but is there a library that provides things like unsafe-vector-length that are actually references to the safe versions? I have a core dump occurring in (someone else's) unsafe code, and I'd much rather just import a different library than go

Re: [racket-dev] safe version of racket/unsafe/ops?

2010-09-27 Thread Jay McCarthy
In principle I think it is a good idea, though I expect me and others will quibble over any name you pick. Jay On Mon, Sep 27, 2010 at 4:04 PM, John Clements cleme...@brinckerhoff.org wrote: I'm sure I'm just missing something obvious here, but is there a library that provides things like

Re: [racket-dev] safe version of racket/unsafe/ops?

2010-09-27 Thread Robby Findler
How about prefix-in with unsafe- as the prefix? Robby On Monday, September 27, 2010, John Clements cleme...@brinckerhoff.org wrote: I'm sure I'm just missing something obvious here, but is there a library that provides things like unsafe-vector-length that are actually references to the

Re: [racket-dev] safe version of racket/unsafe/ops?

2010-09-27 Thread John Clements
On Sep 27, 2010, at 3:45 PM, Robby Findler wrote: How about prefix-in with unsafe- as the prefix? You still have to specify the right set of functions, right? But yes, that's all I'm thinking of. John smime.p7s Description: S/MIME cryptographic signature

[racket-dev] Compile Error

2010-09-27 Thread Everett Morse
Is there something wrong with my build? This happens when I remove everything from my build directory AND with a fresh repository (so it's not something weird I did). I tried a pull on Fri, Sat, and today (Mon), and get this error still. (Using the command git clone

Re: [racket-dev] Compile Error (Everett Morse)

2010-09-27 Thread James Swaine
Do you know, by chance, if your processor supports the SSE2 extensions? It looks like you're compiling on a 32-bit Mac... (In the meantime, if you don't need to use parallel futures, you can work around this by disabling futures in the build. Rerun the configure script and pass