All I did was ask a simple question after RTFM, and after trying several different things, and after using SuperSearch. I'm not an idiot, nor am I lazy.
All I did was answer the question (using your own words no less) without calling you an idiot or lazy.
I can't help if you feel like an idiot.
So yeah, it ought to be really simple. But if that is the case, shouldn't I be able to make the test fail when the two hashes are different?
But it is simple, and you can make the test fail, you just have to write it correctly.
I thought that would be obvious once you understood how cmpStrHard works.
ok( not cmpStrHard(\%crosslinks, \%crosslinkscorrect) );
Another thing I'm curious about: I mentioned that the test unexpectedly succeeded. There really isn't anything interesting when that happens. What information should I have provided?
Something everyone can run that demonstrates your dilemma.
Only you have access to JScan::ReadCrossLinks , ReadCrossLinks, \%crosslinks, \%options...
So PodMaster-- for posting and not actually helping. All I needed was confirmation that I was using FreezeThaw correctly. Too bad you couldn't do that, or at least keep silent.
I know I helped ( I showed you that you're not using FreezeThaw correctly).
I wasn't very explicit and verbose, but i thought it was obvious.
Too bad you didn't get it.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
-
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.
|
