I'd like to point out a few short-comings with List::Compare:
- It stringifies almost everything. Specifically, it does not stringify get_bag(), but it does everything else. This means it will have serious problems working with references.
- It doesn't maintain order. This may not be important in many situations, but a "list" is inherently ordered. Set::Object has similar methods, and actually deals with the appropriate term. :-)
- It has a bug when dealing with lists of code-references without using the -u (unsorted) flag. Specifically, if the first element in your first list is a code-reference, sort will attempt to use it as the sorting method. Which means it's not in the list of things to sort, so it's lost from the bag.
I don't meant to indicate that it's a bad module. Perl lists are ... difficult to deal with. (Oh - it also doesn't deal with lists ... it deals with arrays. But, that's another nit.)
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
-
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.
|