If I were designing a CS curriculum, I would really concentrate on things such as data types/memory, things that perl really doesn't address, in the freshman year. I think that subsequent years are really the place for things such as perl, when you are more into the algorithmic side and such. Yes, these ARE the pitfalls that many freshmen computer science students fall into, but isn't it better to train them to be well disciplined programs with a strong knowledge of what is going on inside the computer from the start, than to listen to them whine about having to do it later? I can certainly see very strong arguments for teaching freshman programming in perl, for one thing, retention would probably be MUCH higher, and you wouldn't lose the students (mentally). I suppose that it is a VERY good idea in those respects. I have just made a circular argument. I suppose that either way, you are really good to go, but I think that my personal approach to it would be something a bit less abstract in nature. Not that I don't like perl guys.
Just Another Perl Hacker
-
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.
|
