scalars don't have a length. Do you mean the string contained within a scalar?
That's why I said "PV" in the title.
However, I recently heard many builtins (index? substr?) use 32-bit indexes.
That would (almost) explain what I'm seeing. I'm returning an SV with the PV set to point at an 8GB lump of memory mapped file. I'm setting CUR and LEN myself, and length duly reflects the numbers I set. But if I try to substr that scalar with an offset > 2**31, it bellyaches about "substr outside of string". Which perhaps suggests that they are doing some signed 32-bit math with what should be unsigned 64-bit values.
I guess I'll have to map the file as N x 2GB lumps so that they'll play nice with substr et al.
Looks like there are still some edges to be knocked off the 64-bit ports.
In reply to Re^2: PV limits on 64-bit perls?
by BrowserUk
in thread PV limits on 64-bit perls?
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |