Email List: Xaustin-review-lX
[All Lists]

Defect in XCU Token Recognition

To: yyyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Defect in XCU Token Recognition
From: yyyy@xxxxxxxx
Date: Mon, 28 Jul 2003 21:06:38 +0100 (BST)
        Defect report from : Miloslav Trmac , N/A

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 32 line 1304,1328-1330 section Token Recognition editorial {rhl100970}

Problem:

Edition of Specification (Year): 2001

Defect code :  1. Error

Currently, XCU 2.3 specifies that shell command language in terms
of <blank>s, which makes the interpretation of any shell script
dependent on the LC_CTYPE category of current locale.

Aside from the obvious result that a single shell script may or
may not work in a different environment, this also puts unnecessary
burden on implementors (effectively requiring a call on isblank ()
on each input character). There is at least one widely used
shell implementation (bash) that in fact does not honor the LC_CTYPE
category.

In order for a script to be portable, it must rely only on <space>
and <tab> characters being interpreted as <blank>. Replacing "<blank>"
by "<space> or <tab>" promotes shell script portability and allows
faster shell implementations.

Action:

On page 32, line 1304, replace
"If the current character is an unquoted <blank>", ...
by
"If the current character is an unquoted <space> or <tab>", ...

On page 32, line 1328, replace
"If the value of the alias replacing the word ends in a <blank>", ...
by
"If the value of the alias replacing the word ends in a <space> or <tab>", ...

On page 32, line 1330, replace
... "that does not end in a <blank>."
by
... "that does not end in a <space> or <tab>."

On page 35, line 1439-1440, remove
"and <blank>s (character class blank).

<Prev in Thread] Current Thread [Next in Thread>