hi,
I think I have found a document bug for expr:
in the info page of "String expressions", it says "`expr' supports
pattern matching and other string operators. These have *lower*
precedence than both the numeric and ...",.
But I think the string expressions have *higher* precedence than
numeric
[EMAIL PROTECTED] wrote:
> I think I have found a document bug for expr:
> in the info page of "String expressions", it says "`expr' supports
> pattern matching and other string operators. These have *lower*
> precedence than both the numeric and ...",.
> But I think the string expressions have *h
Jim Meyering <[EMAIL PROTECTED]> writes:
> @@ -10884,8 +10884,9 @@ To make @command{expr} interpret keywords as strings,
> you must use the
> @cindex expressions, numeric
>
> @command{expr} supports the usual numeric operators, in order of increasing
> -precedence. The string operators (previo
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> @@ -10884,8 +10884,9 @@ To make @command{expr} interpret keywords as
>> strings, you must use the
>> @cindex expressions, numeric
>>
>> @command{expr} supports the usual numeric operators, in order of incr
