Re: errata/257: Should white space be allowed in hierarchical references?

From: Steven Sharp (sharp@cadence.com)
Date: Sat May 03 2003 - 12:10:05 PDT

  • Next message: Shalom Bresticker: "Re: [Fwd: errata/310: PROPOSAL - wrong or poor xrefs]"

    Precedence: bulk

    The following reply was made to PR errata/257; it has been noted by GNATS.

    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
     

    This archive was generated by hypermail 2.1.4 : Sat May 03 2003 - 12:11:00 PDT and
    sponsored by Boyd Technology, Inc.