I agree. I don't think there's any point in shielding people from the truth, but at the same time, there's no point in scaring people off when you can easily avoid it. A better answer to the question might've been:
"The ususal way is to use the perl debugger (point to PODs), but there are graphical altneratives available (preferably point to those)."
I think this highlights a small attitude in the Perl community along the lines of "you're not a *real* developer unless you use vim / *NIX / CLI, etc". Just to emphasise, I do think this is a *small* problem, but not an insignificant one, not least because some of the "higher ups" in the community can sometimes give this impression (even if it's not intentional).
Maybe vim + CLI works for you, but a huge amount of developers prefer to work in a fully functional IDE these days.
-
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.
|