There is nothing wrong with keeping a counter in a module.
This combined with overloading open, close, socket...
so you could keep a valid counter is one possiblity
(not recommended).
Opening until you get an error is better. Even better is
to make the user responsible, and let them set
the maximum (in which case you need not worry about how many they have open).
Defaulting to a reasonable value like 16.
This is much friendlier for a module anyways,
what if I don't want to swamp my box? This is
basically how
FileCache works (hence my jumping the gun below/earlier).
UPDATE: *sigh* Pay no attention to the man behind the curtain
~~~ This is a curtain ~~~
Perl comes with a standard module for handling (UPDATE: the non-socket case of) this,
it is FileCache. Perl 5.8 will have an improved version that
is available over there
(or in bleadperl of course, require perl 5.6+).
--
perl -pew "s/\b;([mnst])/'$1/g"
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.