… | |
… | |
609 | the years (includign some defense in depth mechanism that can shield |
609 | the years (includign some defense in depth mechanism that can shield |
610 | against a lot of as-of-yet undetected bugs), using this library for |
610 | against a lot of as-of-yet undetected bugs), using this library for |
611 | security purposes requires care. |
611 | security purposes requires care. |
612 | |
612 | |
613 | Likewise, file sizes when the uulib library was written were tiny compared |
613 | Likewise, file sizes when the uulib library was written were tiny compared |
614 | to today, so do not expect this library to handle files larger than 2GB. |
614 | to today, so do not expect this library to handle files larger than 2GB, |
|
|
615 | certainly not on a 32 bit host. |
615 | |
616 | |
616 | Lastly, this module uses a very "C-like" interface, which means it doesn't |
617 | Lastly, this module uses a very "C-like" interface, which means it doesn't |
617 | protect you from invalid points as you might expect from "more perlish" |
618 | protect you from invalid pointers as you might expect from "more perlish" |
618 | modules - for example, accessing a file item object after callinbg |
619 | modules - for example, accessing a file item object after calling |
619 | C<CleanUp> will likely result in crashes, memory corruption, or worse. |
620 | C<CleanUp> will likely result in crashes, memory corruption, or worse. |
620 | |
621 | |
621 | =head1 AUTHOR |
622 | =head1 AUTHOR |
622 | |
623 | |
623 | Marc Lehmann <schmorp@schmorp.de>, the original uulib library was written |
624 | Marc Lehmann <schmorp@schmorp.de>, the original uulib library was written |