ISSUE 257

Number 257
Category errata
Synopsis Should white space be allowed in hierarchical references?
State lrmdraft
Class errata-simple
Arrival-DateJan 12 2003
Originator Shalom.Bresticker@motorola.com
Release 2001b: 12.4, 12.5, A.Notes
Environment
Description
Current LRM prohibits white space in hierarchical references
around the . , except after an escaped identifier.

Is this necessary ?

What about hierarchical references to an array instance?
Are spaces allowed around and within the square brackets?
Fix
Delete the restriction that hierarchical references may not
contain spaces.

Specifically:

1. In Syntax 12-7, DELETE the first and second footnotes

("The period in escaped_hierarchical_identifier and
escaped_hierarchical_branch shall be preceded by white_space,
but shall not be followed by white_space.",

"The period (.) in simple_hierarchical_identifier and
simple_hierarchical_branch shall not be preceded or followed
by white_space.")


2. In Section 12.5, DELETE the following paragraph:

"There shall be no spaces within the hierarchical name
reference, except for escaped identifiers embedded in the
hierarchical name reference, which are followed by
separators composed of white space and a period-character."


3. In the NOTES following A.9.5, DELETE Notes 3 and 4.

(These notes are the same as footnotes 1 and 2 in Syntax
12-7, quoted above.)
Audit-Trail
From: "Brad Pierce" <Brad.Pierce@synopsys.com>
To: <etf-bugs@boyd.com>
Cc:
Subject: Re: errata/257: Should white space be allowed in hierarchical references?
Date: Sat, 3 May 2003 10:32:46 -0700

This issue asks whether it's necessary to prohibit white space
around the '.' in an hierarchical identifier.

I think so, else one couldn't convert an hierarchical identifier
into a flattened pseudohierarchical identifer simply by putting
a backslash in front of it. For example,

f( m.x , m.y ) ---> f( \m.x , \m.y )

but not

f( m . x , m . y ) ---> f( \m . x , \m . y )





From: Steven Sharp <sharp@cadence.com>
To: etf-bugs@boyd.com, Brad.Pierce@synopsys.com
Cc:
Subject: Re: errata/257: Should white space be allowed in hierarchical references?
Date: Sat, 3 May 2003 15:08:14 -0400 (EDT)

> I think so, else one couldn't convert an hierarchical identifier
> into a flattened pseudohierarchical identifer simply by putting
> a backslash in front of it. For example,
>
> f( m.x , m.y ) ---> f( \m.x , \m.y )
>
> but not
>
> f( m . x , m . y ) ---> f( \m . x , \m . y )

I don't understand your concern. The white space is not a significant
part of the name. The reference "m . x" represents the same thing as "m.x".
The spaces will presumably be discarded by the parser, producing the same
internal representation for both textual variations of the name. There
should be no problem generating "\m.x" for either one in your scheme.

BTW, how is your scheme supposed to convert a name like "\m.x .y" to
produce a legal name that is distinct from the converted form of "m.x.y"?

Steven Sharp
sharp@cadence.com

From: Shalom.Bresticker@motorola.com
To: Brad.Pierce@synopsys.com
Cc: etf-bugs@boyd.com
Subject: Re: errata/257: PROPOSAL - Should white space be allowed in hierarchical
references?
Date: Sat, 4 Oct 2003 20:14:17 +0200 (IST)

I would prefer to keep this as a separate issue.
Since we do no yet have a clear proposal for 37,
please make a proposal for 257 to delete all the
places that forbid such white space.
I do not have web access or PDF or FM right now.

Thanks,
Shalom


On Fri, 3 Oct 2003 Brad.Pierce@synopsys.com wrote:

> Date: Fri, 3 Oct 2003 13:33:33 -0700
> From: Brad.Pierce@synopsys.com
> To: etf-bugs@boyd.com
> Subject: errata/257: PROPOSAL - Should white space be allowed in hierarchical
references?
>
> Precedence: bulk
>
> Close as duplicate of issue 37.
> http://boydtechinc.com/cgi-bin/issueproposal.pl?cmd=view&pr=257
>

--
Shalom Bresticker Shalom.Bresticker@motorola.com
Design & Reuse Methodology Tel: +972 9 9522268
Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890
POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478


Fix replaced by Shalom.Bresticker@motorola.com on Mon Oct 27 09:03:28 2003
Delete the restriction that hierarchical references may not
contain spaces.

Specifically:

1. In Syntax 12-7, DELETE the first and second footnotes

("The period in escaped_hierarchical_identifier and
escaped_hierarchical_branch shall be preceded by white_space,
but shall not be followed by white_space.",

"The period (.) in simple_hierarchical_identifier and
simple_hierarchical_branch shall not be preceded or followed
by white_space.")


2. In Section 12.5, DELETE the following paragraph:

"There shall be no spaces within the hierarchical name
reference, except for escaped identifiers embedded in the
hierarchical name reference, which are followed by
separators composed of white space and a period-character."


3. In the NOTES following A.9.5, DELETE Notes 3 and 4.

(These notes are the same as footnotes 1 and 2 in Syntax
12-7, quoted above.)

Unformatted


Hosted by Boyd Technology