| 1 |
Paranoid |
| 2 |
======== |
| 3 |
|
| 4 |
NOTICE: One might wonder how we've jumped from 0.x releases to 2.x. I've |
| 5 |
decided to skip the 1.x releases to make it (hopefully) more obvious that |
| 6 |
the API has changed and is not compatible with the 0.x series. My fear was |
| 7 |
that the average devmight see 0.x to 1.x and assume that I was simply |
| 8 |
declaring the API stable. While 2.x is a stable API it is not compatible |
| 9 |
with 0.x. |
| 10 |
|
| 11 |
In addition to the API change there is also a packaging change in that I am |
| 12 |
no longer shipping modules with the core distribution that were essentially |
| 13 |
non-functioning unless you had additional modules installed (outside of the |
| 14 |
mandatory prerequisites). Those modules will still be available, but only |
| 15 |
as their own distributions on CPAN. |
| 16 |
|
| 17 |
With that out of the way I present to you, with no further ado, Paranoid |
| 18 |
v2.0. |
| 19 |
|
| 20 |
-- |
| 21 |
|
| 22 |
The Paranoid suite of modules intend to provide an application framework |
| 23 |
that's designed for secure programming. It has internally consistent |
| 24 |
debugging and tracing capabilities and is tested for use in applications |
| 25 |
with taint-mode enabled in addition to the normal strict and warnings modes. |
| 26 |
The focus of these modules is to make secure programming convenient and |
| 27 |
easy enough that it becomes the developer's default development target, not |
| 28 |
just a feature of special software. |
| 29 |
To that end you will find APIs for a multitude of common tasks, from |
| 30 |
process management to input handling. There are also compatiblity modules |
| 31 |
(like Paranoid::Network::Socket) that can make IPv6 programming |
| 32 |
seemless, regardless of the version of Perl running or its incremental level |
| 33 |
of support for IPv6. |
| 34 |
Each module has its own documentation. You can find a complete list of |
| 35 |
modules in this suite from the Paranoid POD. |
| 36 |
|
| 37 |
Please send bugs, requests, and flames to Arthur Corliss |
| 38 |
<[email protected]>. |