Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Thanks for reply. In fact I used print(variable) system in R (before I found Sci-views), but I was always craving for the possiblity to have a graphical interface allowing to follow values of selected variables line by line - usually the error was caused by some problem well before the line causing program crashed. So having IDE with this capabilities would be nice.

There is no danger that I would become a programming expert enjoying the beauty of the solutions. Too late for me. For me it will be always a mean to get the things done. Is the code ugly? Is it slower than necessary? I don`t care, it works and I can use the output for solving the relevant biology. Are there some general programming tips for the Seekers Of The Way Of The Lowest Resistance like me :-)?


In reply to Re^2: Free Perl IDE for a begginer by karpatov
in thread Free Perl IDE for a begginer by karpatov

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.