On 10/18/07, <b class="gmail_sendername">Shlomi Fish</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Indeed. I always find it a curious fact when Matam/Mamat students were<br>instructed to solve exercises without using sed or awk, or in one line of<br>C-shell. This may indicate that they want to design clever exercises, but not
<br>to really teach the beauty of shell scripting.</blockquote><div><br>Exactly. The point is not to teach the beauty of shell scripting.<br><br>I suggest you'll approach the lecturers in charge to get a better understanding why they teach this shell rather than that shell (like Eyal did).
<br><br>As for the "beauty" thing - beauty is in the eye of the beholder.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well, from what I understood, up to a point TX still carried a Perl that was<br>9-years-old or so (Nadav can fill the details). But even if it didn't carry<br>bash, then bash was easily installable there.</blockquote>
<div><br>Yes and no.<br><br>Unlike what many people think, installing software on a server with multiple users is not as simple as running yum/rpm/whatever your distro is using.<br><br>It is an obligation by the staff to support, update (to some extent), insure backward competability (in the case of updates), etc. The claim that "It's easy to install" is wrong for systems which you do not own, nor understand all the technical (or political) aspects related to.
<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Seeing as C and shell-scripting are used for inherently different purposes,
<br>> I do not see why this is an advantage; furthermore, I think that in the<br>> exercises which are being taught, far too much stress is being put on loops<br>> and "if" statemenets; Too little on effective usage of "&&" and "||"
<br>> operators. Also, extremely useful unix commands such as sed and find are<br>> not taught, and I have actually seen an exercise given in the course where<br>> the students implement a crippled version of "find". More relevant uses for
<br>> shell scripts are never brought as an example - students are not shown, for<br>> example, how to use them in conjunction with "make" in order to create a<br>> test suite for their programs. If you want to teach scripting - use a
<br>> scripting language (preferably something more organized than perl, like<br>> Python). If you want to teach SHELL scripting, the exercises must be<br>> relevant to that style of programming.<br><br>Right.</blockquote>
<div><br>Please note that the idea is not to teach UNIX, but to teach on the existance of a tool called shell scripting.<br>For us it is very easy to say "yeah, this can be solved by find". But these students need to learn how to implement find in a crippled scripting language, because when they'll leave the academy and go to the dark side,
a.k.a., industry, they will have to work on machines which are not even POSIX complaint!<br><br>People, please remember we are talking on a degree in computer science (or EE), i.e., you do not learn JAVA, you learn OOP methodology (for example, by using JAVA). These two things are completely different.
<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> * One-liners are not possible - blocks have to start on separate lines.<br>
> This makes tcsh very uncomfortable to use in interactive mode.<br><br>I know and I've explicitly mentioned it in my original article:<br><br><<<<<<<br>Entire Bash mini-programs can be written, tested and debugged in one line.
<br>This is impossible to do in csh which forces loops to be on separate lines.<br>>>>>>></blockquote><div><br>oh, these kids who never worked on COBOL... ;) <br></div></div>-- <br>Orr Dunkelman,<br><a href="mailto:Orr.Dunkelman@gmail.com">
Orr.Dunkelman@gmail.com</a><br><br>"Any human thing supposed to be complete, must for that reason infallibly<br>be faulty" -- Herman Melville, Moby Dick.<br><br>GPG fingerprint: C2D5 C6D6 9A24 9A95 C5B3 2023 6CAB 4A7C B73F D0AA
<br>(This key will never sign Emails, only other PGP keys. The key corresponds to <a href="mailto:email@example.com">firstname.lastname@example.org</a>)