ISSUE 119

Number 119
Category errata
Synopsis 2.6.3 (Table 1): Octal escape sequences
State lrmdraft
Class errata-discuss
Arrival-DateSep 16 2002
Originator Shalom.Bresticker@motorola.com
Release 2001b: 2.6.3 (Table 1), 17.1.1.1 (Table 66)
Environment
Description
---------- Forwarded message ----------
Date: Mon, 16 Sep 2002 08:58:48 -0700
From: Brad Pierce <Brad.Pierce@synopsys.com>


1) The last row of Table 1 is inconsistent. The left column shows
three digits required, but the right column says 1--3 digits are
allowed.

2) If 1--3 digits were allowed, the syntax would be ambiguous. Is \177
the rubout character or is it the shift-in character followed by a 7 or
is it the start-of-heading character followed by two 7's?

3) What is the meaning of \200? Should the first digit be restricted
to <= 1?





Fix
In Table 1 of section 2.6.3


REPLACE:

A character specified in 1-3 octal digits (0<= d <= 7)

WITH:

A character specified in 1-3 octal digits (0 <= d <= 7).
If less than three characters are used, the following
character must not be an octal digit. Implementations
may issue an error if the character represented is
greater than \377.

***********************
Note:

Same change in Table 66 in 17.1.1.1
***********************

Audit-Trail

Analized by etf@boyd.com on Thu Dec 12 13:07:36 2002
In Table 1 of section 2.6.3

Replace:

/ddd

With

/d<any non-numeric character>
/dd<any non-numberic character>
/ddd







Note: because strings can represent arbitrary bit sequences,
we should allow any numbers in any position.>Unformatted:


Analyzed by Shalom.Bresticker@motorola.com on Wed Mar 19 05:10:11 2003
It was pointed out in the last VSG meeting that \199 is not
a valid octal number, and sent back to the ETF.
Should it be \177 or \377 ?
Note that \177 is the rubout character.

OLD PROPOSAL:

In Table 1 of section 2.6.3

REPLACE:

A character specified in 1-3 octal digits (0<= d <= 7)

WITH:

A character specified in 1-3 octal digits (0 <= d <= 7).
If less than three characters are used, the following
character must not be an octal digit. Implementations
may issue an error if the character represented is
greater than \199.

Same change in Table 66 in 17.1.1.1


From: Steven Sharp <sharp@cadence.com>
To: etf-bugs@boyd.com, Shalom.Bresticker@motorola.com
Cc:
Subject: Re: errata/119: ANALYZED - 2.6.3 (Table 1): Octal escape sequences
Date: Wed, 19 Mar 2003 13:16:33 -0500 (EST)

I believe it should be \377, not \177. I don't see any reason not to allow
full 8-bit characters.

Steven Sharp
sharp@cadence.com

Unformatted


Hosted by Boyd Technology