I started putting print statements in the methods of the package and they were printing on STDOUT ... Suddenly they stopped.
So either the way modules work suddenly changed, or else something in your code and/or system did. I just want to reinforce the idea, already expressed directly or indirectly by other monks, that the latter possibility is by far the most likely.
Are you even working on the code you think you're working on? Have you inadvertently started working on a different set of similar or identical files? I remember a jolly hour or two I once spent debugging some C/C++ code. I happily tried one fix after another; none had any effect. I finally noticed that one of the changes I had made was not syntactically correct, but had compiled anyway. I tried inserting the magical snifiasdha; statement and compiling again. The compiler was still happy. The penny finally dropped. It turned out that another programmer had placed a huge block of code into a
#if 0
...
...
#endif
"block comment" that my syntax highlighter could not detect, and I had been "debugging" dead code. Massive facepalm. Thus do we live and learn.
Give a man a fish: <%-{-{-{-<
-
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.
|