[uClibc] Re: Why use perl instead of sed to hack binutils, gcc
tom at ceisystems.com
tom at ceisystems.com
Mon Oct 6 06:27:17 UTC 2003
Miles,
This is what Erik said he was trying to avoid. I think the KISS
approach he takes is a bit simpler. It leaves less to be forgotten.
And everybody here has forgotten something critical at one time or
another (i.e. Car Keys, closing brace, semi-colon, the number of "911").
Thomas Cameron
CEI Systems
P.S. I am NO fan of PERL, but sometimes evil is necessary. Besides, it
works Well Enough(tm)
> -----Original Message-----
> From: uclibc-bounces at uclibc.org
> [mailto:uclibc-bounces at uclibc.org] On Behalf Of Miles Bader
> Sent: Sunday, October 05, 2003 10:50 PM
> To: andersen at codepoet.org
> Cc: uclibc at uclibc.org
> Subject: [uClibc] Re: Why use perl instead of sed to hack
> binutils, gcc
>
>
> Erik Andersen <andersen at codepoet.org> writes:
> > I use perl since perl allows me to edit files in place.
> > Sed edits copies, which must them be moved into place on
> > top of the original file, which is a bit more dangerous,
>
> Er, well there's always
>
> sed FOO < file > file.new && mv file.new file
>
> That's what I always use; even when on a big system, the idea
> of starting a bloated monster like perl just to do a simple
> replace seems somehow ... offensive.
>
> [Perl's binary is _35 times_ the size of GNU sed on debian,
> BTW... Ouch!]
>
> -Miles
> --
> `To alcohol! The cause of, and solution to,
> all of life's problems' --Homer J. Simpson
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc
>
More information about the uClibc
mailing list