home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.shell:3824 comp.unix.questions:10738
- Path: sparky!uunet!mcsun!uknet!axion!spuddy!sweh
- From: sweh@spuddy.uucp (Stephen Harris)
- Newsgroups: comp.unix.shell,comp.unix.questions
- Subject: Re: Shell Scripts vs. C programs
- Keywords: shell script, C
- Message-ID: <1992Sep3.213336.5151@spuddy.uucp>
- Date: 3 Sep 92 21:33:36 GMT
- References: <119@steiny.com> <1992Sep1.222041.1491@spuddy.uucp> <123@steiny.com>
- Organization: Spuddy's Public Usenet Domain
- Lines: 29
-
- In article <123@steiny.com> steiny@steiny.com (Don Steiny) writes:
- > This may be a matter of scale, but 1000 lines is not a very large
- >program. Besides, there are still many systems that do not have ksh,
- >unfortunately, I have to use them all the time. Even on Sun's, ksh is
- >a "local" program and is not always there.
-
- You're right - 1000 lines of C code is not a lot. 1000 lines of shell script
- in one program is quite a bit. (This was just the main message router program.
- The whole system comes close to 7000 lines).
- On one of the machines, once I had ksh compiled OK, it was easier to write
- ksh scripts than c programs (Altos 3068). Heck! On this machine the C
- compiler would barf on its own include files!
- #include <machine.h>
-
- That one line program through up tonnes of cpp errors. Blugh.
-
- >a different kettle of fish than 20,000+ line program that run on dozens of
- >systems. Ask Larry Wall, the author of perl and rn. He wrote perl
- >partially because of the portablity problems with the shell.
-
- I would NEVER write 20,000+ line program in script.
- In fact, I would try hard and not write a 20,000 line program!
- 20 1,000 lines programs sound better :-) And these 1,000 lines programs
- I *might* write in ksh.....
- --
- Stephen Harris
- sweh@spuddy.uucp ...!uknet!axion!spuddy!sweh
-
- * Meeeeow ! Call Spud the Cat on > +44 203 638780 < for free Usenet access *
-