Thanks a lot for the positive review. Just to add a few points:
- Additional formats supported:
- "Range" notation such as in 10.10.10.0-255 for 10.10.10/24
- Cisco's wildcard notation
- inet_aton and inet_ntoa to feed directly to old-style socket calls
- The code has been tested in the following platforms by the author: Solaris/Sparc, Linux/Intel, FreeBSD/Intel, Win32/Intel, Digital Unix/Alpha, HP-UX/PA-RISC, Mac OS X/PPC. No reports of endianness-related problems have been received so far.
If you're running a version earlier than 3.00, please do consider upgrading. 3.xx includes vast performance improvements in many operations as well as a simpler internal representation guaranteed to be portable to any machine with 32 bits integers.
Best regards
-lem, but some call me fokat
Update: I mistakenly mentioned 3.20 before it came into existence. Current versions as of this writing are 3.14 (production) and 3.14_1 (development, with fresh patches for IPv6).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
