Re: [racket-dev] [plt] Push #25302: master branch updated

On Aug 31, 2012, at 3:07 PM, mfl...@racket-lang.org wrote: > mflatt has updated `master' from eed93825ab to 7b2e18afc5. > http://git.racket-lang.org/plt/eed93825ab..7b2e18afc5 > > =[ 2 Commits ]== > Directory summary: > 11.6% collects/rac

Re: [racket-dev] desired behavior of (in-directory …) when lacking permissions?

At Fri, 31 Aug 2012 09:55:04 -0700, John Clements wrote: > #lang racket > > (sequence->list (in-directory "/tmp/f")) > > … produces this pair of errors: > > . . plt/collects/racket/private/for.rkt:1857:28: directory-list: could not > open directory > path: /tmp/f/sekrit > system error: Perm

[racket-dev] desired behavior of (in-directory …) when lacking permissions?

Currently, using the (in-directory …) sequence in a directory where there are unreadable directories causes a funny internal contract failure. Suppose I have directory "/tmp/f", containing directory "sekrit" which I cannot read. Then this program: #lang racket (sequence->list (in-directory "/t

Re: [racket-dev] [racket] Profiling mostly macro-generated definitions?

Sorry that I've been slow to catch on in this thread... Yes, stack traces in JIT mode don't really work in Win64, and that's why `profile' gives no information. I'll try to improve Win64 context support sometime soon. At Fri, 31 Aug 2012 07:05:14 -0500, Robby Findler wrote: > >> I believe I'm usi

Re: [racket-dev] [racket] Profiling mostly macro-generated definitions?

>> I believe I'm using the 32 bit build in all those cases, tho. Are you >> using the 64 bit one? > > Yes. Thanks. I see this too. Here's a shorter program illustrating the difference. #lang racket (require profile) (define (f x) (if (zero? x) (continuation-mark-set->context (cur