Jos� Augusto Vasconcellos Neto wrote:
>
> I don't received the original question but I can write about sed
> and awk.
>
> 'sed' is a stream editor, with very complicated commands derived
> from the old editor 'ed'. It's suited for edit pipelines on shell
> scripts, and I've used it occasionally for little hacks.
>
> 'awk' is a surprisingly powerful interpreted language, for
> text processing and number crunching. It is old fashioned, but
> resembles C and perl. I like it and use it very much to process
> and analyze data in text files. It's also useful for extracting
> reports (remember perl!? ;). I have some statistical scripts in
> awk and I think it is very fast to prototype little and medium
> sized applications. But I think nearly nobody is using it nowadays.
> > Perl is very nice for text processing (it is not a word processor though :-)
> > and number crunching. I find Perl a very easy language to program in. It has
> > only one problem, it does not compile too well. The only compiler I could
> > find and try did not do a very good job.
Perl is a compiled language. it compiles quite nicely on
various perl engines. translating it into C is a fairly
new feature (5.005), which may be what you're describing
as having holes.
main differences between perl and awk/sed/shell is that perl
is a compiled language, with the engine running bytecodes
produced from the input program at runtime.
--
Steven Lembark 2930 W. Palmer St.
Workhorse Computing Chicago, IL 60647
[EMAIL PROTECTED] 800-762-1582
---------------------------------------------------------------------
The opinions expressed here are those of this company.
I am the company.
---------------------------------------------------------------------
S/MIME Cryptographic Signature