Re: Reducing KODRETRY
"Steven W. Orr" <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Organization | SysLang |
| Message-ID | <[email protected]> |
On Wednesday, Dec 27th 2006 at 03:21 -0500, quoth Ryan Barrett: =>On Wed, 27 Dec 2006, Thorsten Glaser wrote: => =>> > http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/ =>> =>> While I do agree on that, this is not intended as a shell flamewar... I => =>agreed, -1 to flame wars, but i have to qualify steven's citation. => =>"CSH Programming Considered Harmful" argues convincingly that csh and friends =>are inappropriate for *programming*, ie writing shell scripts. sadly, it's =>often misused to discourage using csh shells for *any* task, including as =>interactive shells. that's a shame. => =>i've used tcsh as my interactive shell for a long time. i prefer it due to a =>few features, mostly in its line editor, that give it the edge over bash for =>me. (but yes, i also use and love readline in other programs. :P) => =>sure, when i have to write non-trivial shell scripts, i turn to bash. i have =>no problem using one shell for scripting and another for interactive, though. =>use the best tool for the job (and for you), right? The idea of one shell as your login and another for scripting just falls down. One simple example is something I (we) do all the time that can't be done in csh prog 2> /dev/null and the paper ref'd above can produce hundreds of other examples. If you think that using shell interactively and programming scripts are different then we're in different worlds. My overall philosophical high-level view is that if we sit in front of 'puters, especially for a living, then the really simple basics like the shell you log in with and the choice of editor you use (be it emacs *or* vi ;-) are things that you should be powerusers with. If you write a script and feel that bash is too big for your 1Gig memory platform then that's fine. I'm just advocating that there are csh and Bourne flavored shells and the differences are severe. I haven't heard of mksh before but I definitely will look into it. Personally, I find that the best actual interpreter to use in scripts is ksh over bash but it is not alas installed by default everywhere. Just as long as you don't use *csh. :-) _______________________________________________ Pine-info mailing list [email protected] http://mailman1.u.washington.edu/mailman/listinfo/pine-info