Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Gregory Cooper
* Greg Cooper g...@cs.brown.edu - FrTime Tests Done. _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] wrong line marked as source of error?

2011-10-18 Thread Robby Findler
I think this is probably due to a fairly fundamental problem in the way that Racket builds stacks. The whole process is pretty complex, but at a high-level, there are two ways that stack information is obtained: one way (via the errortrace library) is very accurate when it exists, but it does not

Re: [racket-dev] wrong line marked as source of error?

2011-10-18 Thread Robby Findler
Oh, and one more comment: did you try clicking on the left-hand little red icon? That shows you the part of the stack that is in other files (if there is any to be shown). On Tue, Oct 18, 2011 at 6:36 AM, Marijn hk...@gentoo.org wrote: Hi list, while running some code I'm working on, I

Re: [racket-dev] wrong line marked as source of error?

2011-10-18 Thread Marijn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/18/11 14:09, Robby Findler wrote: Oh, and one more comment: did you try clicking on the left-hand little red icon? That shows you the part of the stack that is in other files (if there is any to be shown). I did try that, but it didn't

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Matthew Flatt
At Mon, 17 Oct 2011 19:02:36 -0600 (MDT), Ryan Culpepper wrote: * Matthew Flatt mfl...@cs.utah.edu - Racket Tests - Languages Tests - GRacket Tests (Also check that `gracket -z' and `gracket-text' still works in Windows and Mac OS X) Done. - mzc Tests No longer applies; please

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Jay McCarthy
On Mon, Oct 17, 2011 at 7:02 PM, Ryan Culpepper r...@cs.utah.edu wrote: * Jay McCarthy jay.mccar...@gmail.com  - Web Server Tests  - XML Tests  - HTML Tests  - PLAI Tests  - Racklog tests  - Datalog tests All passed -- Jay McCarthy j...@cs.byu.edu Assistant Professor / Brigham Young

[racket-dev] while resizing drawing into a canvas is off

2011-10-18 Thread Marijn
Dear list, the attached program draws a grid in a canvas and paints a few of the cells so created. When resizing the window, the grid is also dynamically resized together with the coloring of a few painted cells. Everything seems to work fine, except that while the window is being changed in size

Re: [racket-dev] while resizing drawing into a canvas is off

2011-10-18 Thread Matthew Flatt
At Tue, 18 Oct 2011 16:32:54 +0200, Marijn wrote: the attached program draws a grid in a canvas and paints a few of the cells so created. When resizing the window, the grid is also dynamically resized together with the coloring of a few painted cells. Everything seems to work fine, except that

Re: [racket-dev] wrong line marked as source of error?

2011-10-18 Thread Robby Findler
On Tue, Oct 18, 2011 at 8:39 AM, Marijn hk...@gentoo.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/18/11 14:09, Robby Findler wrote: Oh, and one more comment: did  you try clicking on the left-hand little red icon? That shows you the part of the stack that is in other files

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Doug Williams
* Doug Williams m.douglas.willi...@gmail.com - Additional Plot Tests Done. I have removed the plot extensions from the science collection since they aren't needed anymore. The science collection and simulation collection have been updated to use the new plot package - no changes to user

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Jon Rafkind
On 10/17/2011 07:02 PM, Ryan Culpepper wrote: Checklist items for the v5.2 release * Jon Rafkind rafk...@cs.utah.edu Release tests for (one of the) linux releases: - Test that the `racket' and `racket-textual' source releases compile fine (note that they're still called `plt' and

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Stephen Chang
* Stephen Chang stch...@ccs.neu.edu - Lazy Racket Tests - Lazy stepper tests All passed. On Mon, Oct 17, 2011 at 9:02 PM, Ryan Culpepper r...@cs.utah.edu wrote: Checklist items for the v5.2 release  (using the v5.1.900.1 release candidate build) Search for your name to find relevant

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Carl Eastlund
On Mon, Oct 17, 2011 at 9:02 PM, Ryan Culpepper r...@cs.utah.edu wrote: * Carl Eastlund c...@ccs.neu.edu  - Dracula Tests (confirm that Dracula runs from PLaneT) Done. --Carl _ For list-related administrative tasks:

Re: [racket-dev] Pre-Release Checklist for v5.2

2011-10-18 Thread Neil Toronto
On 10/17/2011 07:02 PM, Ryan Culpepper wrote: * Neil Torontoneil.toro...@gmail.com - Plot Tests All passed. Neil T _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev

[racket-dev] async-channels use a manager thread

2011-10-18 Thread Tony Garnock-Jones
Hi all, Why does the implementation of async-channels use a manager thread internally? Is it for kill-safety? Some other reason? Regards, Tony _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] Windows ffi's 'malloc raw' can't be paired with C 'free'

2011-10-18 Thread Matthew Flatt
At Tue, 18 Oct 2011 15:27:28 -0700, John Clements wrote: It looks like there's a problem with the ffi implementation of (malloc ... 'raw) in Windows. In particular, if I call 'free()' in a C extension on a block of memory that was allocated with (malloc ... 'raw), I get the Windows

Re: [racket-dev] Windows ffi's 'malloc raw' can't be paired with C 'free'

2011-10-18 Thread John Clements
On Oct 18, 2011, at 3:36 PM, Matthew Flatt wrote: At Tue, 18 Oct 2011 15:27:28 -0700, John Clements wrote: It looks like there's a problem with the ffi implementation of (malloc ... 'raw) in Windows. In particular, if I call 'free()' in a C extension on a block of memory that was

Re: [racket-dev] Windows ffi's 'malloc raw' can't be paired with C 'free'

2011-10-18 Thread Matthew Flatt
At Tue, 18 Oct 2011 15:39:13 -0700, John Clements wrote: 1) This is only a problem under Windows, right? Yes. 2) It looks to me like there's an easy workaround in my case, which is simply to put the 'malloc' on the C side in a one-line stub function. Right? Yes --- a malloc() in the same