You might want to make the interface to that method a little more
consistent.
You pass in a list, but get back a reference.
If the list is expected to be small all/most of the time,
you might as well use lists. If you think it's going to
be big most of the time, go ahead and pass a reference in and
Just read about a couple resources that I think are pretty nifty.
http://www.cpanforum.com/ provides a thread for each disitrubution on
cpan. You can subscribe, via rss or email, to specific distributions.
http://annocpan.org/ allows people to put annotations next to specific
parts of the documen
This isn't a perl solution, but it may work for you.
You can use the unix split command to split a file into several other
files with the same number of lines each. For that to work, you'll first
have to use tr to convert the ^] record separators into newlines. Then
use tr to convert them all back
I think it's a mistake to get hung up on the leader being "next to" the
fields or the indicators being "next to" the subfields. The leader and
indicators aren't really different than fields and subfields. They were
given special treatment in ISO 2709 due to the limitations of ISO 2709.
If we're mov
I don't remember if it focuses on any particular aspect of programming,
but you might try the working the Python Challenge[1] in Perl.
/dev
[1] http://www.pythonchallenge.com/
-Original Message-
From: Mike Barrett [mailto:coffeeisl...@gmail.com]
Sent: Monday, July 11, 2011 4:07 PM
To:
I just recently came across this presentation which lays out pretty much all
the issues with Unicode in perl, and makes some recommendations for best
practices. You may find some general insight into the whole situation by going
over it.
http://www.slideshare.net/nickpatch/fundamental-unicode-a
