[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: \c escape within $'...' can produce mangled UTF-8
From: |
Mike Frysinger |
Subject: |
Re: \c escape within $'...' can produce mangled UTF-8 |
Date: |
Sun, 15 Aug 2010 12:59:55 -0400 |
On Sun, Aug 15, 2010 at 6:02 AM, Dmitry Groshev wrote:
> On 15/08/2010, Dennis Williamson wrote:
>> It only consumes two bytes on my system (or one if it's followed by
>> another escape or a closing quote).
>
> You are wrong.
you might want to try being less abrasive if you expect people to help you
>> It's the responsibility of your code to put an ASCII character after
>> the \c.
>
> My code is fine, thank you. ;-) Given that I never had any use for
> "\c" when there is "\x".
garbage in -> garbage out
-mike
- \c escape within $'...' can produce mangled UTF-8, Dmitry Groshev, 2010/08/14
- Re: \c escape within $'...' can produce mangled UTF-8, Chet Ramey, 2010/08/14
- Re: \c escape within $'...' can produce mangled UTF-8, Dmitry Groshev, 2010/08/14
- Re: \c escape within $'...' can produce mangled UTF-8, Andre Majorel, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8, Dennis Williamson, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8, Andreas Schwab, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8, Dmitry Groshev, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8, Andreas Schwab, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8,
Mike Frysinger <=
- Re: \c escape within $'...' can produce mangled UTF-8, Dmitry Groshev, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8, Mike Frysinger, 2010/08/15
- Re: \c escape within $'...' can produce mangled UTF-8, Greg Wooledge, 2010/08/16