Re: quote removal issues within character class

From	L A Walsh <bash@tlinx.org>
Newsgroups	gnu.bash.bug
Subject	Re: quote removal issues within character class
Date	2019-11-09 06:46 -0800
Message-ID	<mailman.1108.1573310775.13325.bug-bash@gnu.org> (permalink)
References	<CAH7i3Lr68CiVXLR9_HoOgQa7Vd-zyVZ+fck-0K3uQPTNSirU2Q@mail.gmail.com> <CAH7i3LrZFvJ1ELJzTdQzF1tTqhi9FDrA7xWWYWrd4RgWJs0Wtg@mail.gmail.com> <16736.1573257142@jinx.noi.kre.to> <14879.1573303743@jinx.noi.kre.to> <5DC6D12D.6040900@tlinx.org>

Show all headers | View raw

On 2019/11/09 04:49, Robert Elz wrote:
> There's also
>
> 	The special characters '.', '*', '[', and '\\'
> 	(<period>, <asterisk>, <left-square-bracket>, and <backslash>,
> 	respectively) shall lose their special meaning within a bracket
> 	expression.
>   
----
Is this really what the standard says, because '\\' is not a character, but
2 characters.  They could use "\\" but if a backslash is between single
quotes, it loses its special meaning.  The only way to get a backslash
when using single quotes that I've found is to end the single-quote
then use the backslash.  So if you wanted to insert single quotes in
a string that is single-quoted, you would have to do this:

'this is a single-quote(SQ) quoted string using a SQ ('\'') within
the single quote.' 

Alternatively using double-quotes or another quoting
mechanism might be preferable.

I find it odd that the standard would try to use a backslash within
a SQ'd string as a literalizer.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: quote removal issues within character class L A Walsh <bash@tlinx.org> - 2019-11-09 06:46 -0800

csiph-web