[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sed usage in autoheader
From: |
Johan Danielsson |
Subject: |
Re: sed usage in autoheader |
Date: |
16 Nov 2000 20:00:30 +0100 |
User-agent: |
Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 |
Paul Eggert <address@hidden> writes:
> > From: Akim Demaille <address@hidden>
> > Do you mean `s,[^/]*$,,' would work here?
Yes.
> Just for the record, Cray is correct: POSIX does not allow
> `s/[^/]*$//'. `s,[^/]*$,,' is required to work, though.
How does POSIX differ from Single UNIX in this respect? From the
latter I can possibly deduce that it's undefined.
> I've had good luck with strings like `/foo[\/]bar/' in cases where I
> already know from context that the matched string can't contain `\'.
> That's portable, as it works with both the traditional and the POSIX
> interpretation.
I'm not sure I get it. Do you mean as in "s/foo[\/]bar/xxx/"? If so,
this isn't allowed by SUS ([\/] means backslash or slash, not just
slash).
Anyway, the solution in this case is simple, just change autoheader.
/Johan
- sed usage in autoheader, Johan Danielsson, 2000/11/15
- Re: sed usage in autoheader, Bruce Korb, 2000/11/15
- Re: sed usage in autoheader, Akim Demaille, 2000/11/15
- Re: sed usage in autoheader, Paul Eggert, 2000/11/15
- Re: sed usage in autoheader, Bruce Korb, 2000/11/15
- FYI: Sed portability (Was: sed usage in autoheader), Akim Demaille, 2000/11/16
- Re: FYI: Sed portability (Was: sed usage in autoheader), Johan Danielsson, 2000/11/16
- Re: FYI: Sed portability (Was: sed usage in autoheader), Paul Eggert, 2000/11/16
- Re: sed usage in autoheader,
Johan Danielsson <=