Oh how I concur - actually, I was quite shocked to hear
this coming from you, merlyn - no particular reason.
When I was studying CS in college, I was a lab assistant.
I learned very quickly to code in small chunks - and
save often - revision control was also a big plus.
I learned this, but most of the first and second year CS
majors refused to work in this manner. It was a shame to
watch them type about 100 lines of code, try to compile it,
and then ask me to help figure out what these 200 lines of
errors meant.
<CONTROVERSY>
To tell the truth, the only debugger I found helpfull
is the one that is available for Visual Basic.
</CONTROVERSY>
Jeff
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)
-
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.
|
