True - perhaps it would be best for createjmf to handle the floating point conversion simply to integer for now but be able to deal with floating point -> big int later. That is, handle it "under the covers" within createjmf (and related fns) to allow for future expansion.
On Mon, Sep 15, 2008 at 5:20 PM, Raul Miller <[EMAIL PROTECTED]> wrote: > On Mon, Sep 15, 2008 at 5:16 PM, Devon McCormick <[EMAIL PROTECTED]> > wrote: > > Chris - maybe you shouldn't - what about large files? > > > > For files with sizes>2^32, you'll want to represent the size as a pair of > > integers the way the "bigfiles" module does. Maybe you should keep it > > floating point and include a warning about the behavior to allow for this > > possibility. > > The problem is that createjmf winds up calling OS functions for > some operations, and those OS functions do not do what you think > they might be doing when you give them the wrong data types. > > Coercing floats to integer when calling the OS will fix the immediate > problem. Supporting big files is a different issue and would probably > require using a different set of OS functions. > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > -- Devon McCormick, CFA ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
