[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cwrapper generates long strings.
From: |
Ingo Krabbe |
Subject: |
Re: cwrapper generates long strings. |
Date: |
Sat, 2 Oct 2010 11:06:46 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Sat, Oct 02, 2010 at 08:32:24AM +0200, Ralf Wildenhues wrote:
> > + $SED -n -e '
> > +s/^\(.\{79\}\)\(..*\)/\1\n\2/
>
> \n is portable only in the regex part, but not in the replacement part.
> For that you need backslash then literal newline.
>
This answer contains a part of my most burning questions about libtool
development:
A- what system tools are allowed to assume portability
(sed,tr,ed, ...)
B- what shell version to be assumed or which shell features might be
used. Especially I think about `info bash
"basic shell features" "shell expansions" "shell
parameter expansion"`
C- what about writing parts as compiled programs? Some parsing
tasks could be done much faster and solid through real C
code or what about perl.
bye ingo