Subject: | not mapping non-binary handle |
Date: | Thu, 18 Nov 2010 12:07:47 +1100 |
To: | bug-File-Map [...] rt.cpan.org |
From: | Kevin Ryde <user42 [...] zip.com.au> |
In File::Map 0.30 is it only a warning to map a handle with an encoding
layer?
In my locate iterator thingie I try to choose between mmap and plain i/o
according to whether I'll see the same from an mmap as from read().
I liked it better as an error attempting to mmap a non-binary handle.
I'd like to have either an option for an error, or alternately expose
the _check_layers() func so that I can enquire as to how the layers look
from an mmap perspective.
The name check_layers() might instead be something about "mmap clean" or
"transforming layers" or "rawness" but in any case could say if I ought
to see the same from mmap as from read(), as far as the perlio layers go
at least.
--
The most important thing when choosing fish is freshness. Whenever I
buy seafood extender I make sure it was thawed no more than 2 hours ago.