Mapped files are mapped to memory. How would this memory be addressed if its size > 2^32?
On 64-bit platforms integer is also 64 bit. > From: Devon McCormick <[EMAIL PROTECTED]> > > 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. > > Regards, > > Devon > > On Mon, Sep 15, 2008 at 4:54 PM, Chris Burke wrote: > > > [EMAIL PROTECTED] wrote: > > > I think I have found out what is happening. If I run the previous > > example > > > manually but use <.sz in place of sz in the createjmf_jmf_ line, then the > > > map_jmf_ line works correctly. > > > > > > Maybe sz as originally assigned (i.e 7!;5 <'a') is represented as a > > > floating point number and <.sz is represented as an integer; the one > > > causes createjmf_jmf_ to generate a bad header while the other > > > works. > > > > > > I am not knowledgeable enough to confirm this from the code in the 'jmf' > > > script > > > but it is just a suggestion. > > > > This is correct - createjmf requires an integer argument. I'll fix it to > > coerce a float to integer. Thanks for pointing this out. > > ---------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
