… | |
… | |
596 | security purposes requires care. |
596 | security purposes requires care. |
597 | |
597 | |
598 | Likewise, file sizes when the uulib library was written were tiny compared |
598 | Likewise, file sizes when the uulib library was written were tiny compared |
599 | to today, so do not expect this library to handle files larger than 2GB. |
599 | to today, so do not expect this library to handle files larger than 2GB. |
600 | |
600 | |
|
|
601 | Lastly, this module uses a very "C-like" interface, which means it doesn't |
|
|
602 | protect you from invalid points as you might expect from "more perlish" |
|
|
603 | modules - for example, accessing a file item object after callinbg |
|
|
604 | C<CleanUp> will likely result in crashes, memory corruption, or worse. |
|
|
605 | |
601 | =head1 AUTHOR |
606 | =head1 AUTHOR |
602 | |
607 | |
603 | Marc Lehmann <schmorp@schmorp.de>, the original uulib library was written |
608 | Marc Lehmann <schmorp@schmorp.de>, the original uulib library was written |
604 | by Frank Pilhofer <fp@informatik.uni-frankfurt.de>, and later heavily |
609 | by Frank Pilhofer <fp@informatik.uni-frankfurt.de>, and later heavily |
605 | bugfixed by Marc Lehmann. |
610 | bugfixed by Marc Lehmann. |