[racket-dev] File is really large (> 5 MB), really open?

2010-09-26 Thread John Clements
I accidentally opened a sound file in DrRacket today; cue six minutes of thrashing and computer unhappiness. Would it be okay if I added a second-check dialog to DrRacket that checked the size of a file before opening it, and asked for confirmation before opening files larger than, say, 5MB?

Re: [racket-dev] File is really large (> 5 MB), really open?

2010-09-26 Thread Robby Findler
Sure! Robby On Sun, Sep 26, 2010 at 11:14 AM, John Clements wrote: > I accidentally opened a sound file in DrRacket today; cue six minutes of > thrashing and computer unhappiness.  Would it be okay if I added a > second-check dialog to DrRacket that checked the size of a file before > opening

[racket-dev] u8vector->cpointer documented but unimplemented

2010-09-26 Thread John Clements
The function u8vector->cpointer is documented, but doesn't exist; this is presumably because the u8vector functions are actually byte-string functions, but it's not clear to me whether the absence of u8vector->cpointer is an oversight or whether it would violate abstractions in bad ways and henc

Re: [racket-dev] u8vector->cpointer documented but unimplemented

2010-09-26 Thread Matthew Flatt
At Sun, 26 Sep 2010 10:18:13 -0700, John Clements wrote: > The function u8vector->cpointer is documented, but doesn't exist; this is > presumably because the u8vector functions are actually byte-string functions, > but it's not clear to me whether the absence of u8vector->cpointer is an > oversi

Re: [racket-dev] File is really large (> 5 MB), really open?

2010-09-26 Thread Jake Eakle
I would humbly suggest that this dialog should, in order of ease-to-implement a) display the size of the file, b) let the user know why they might not wish to proceed, and c) give some indication of how much memory they should probably have in order to expect reasonable performance. Jake On Sun,

Re: [racket-dev] File is really large (> 5 MB), really open?

2010-09-26 Thread John Clements
On Sep 26, 2010, at 9:58 PM, Jake Eakle wrote: > I would humbly suggest that this dialog should, in order of ease-to-implement > > a) display the size of the file, > b) let the user know why they might not wish to proceed, and > c) give some indication of how much memory they should probably hav