home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.iso
- Path: sparky!uunet!walter!wrench!tain
- From: tain@wrench.bae.bellcore.com (Tai Nguyen)
- Subject: Re: Re:
- Message-ID: <1992Sep8.212341.28488@walter.bellcore.com>
- Sender: news@walter.bellcore.com
- Nntp-Posting-Host: wrench.bae.bellcore.com
- Organization: Bell Communications Research
- References: <86010002@hpcndaw.CND.HP.COM> <86010003@hpcndaw.CND.HP.COM>
- Date: Tue, 8 Sep 92 21:23:41 GMT
- Lines: 34
-
- In article <86010003@hpcndaw.CND.HP.COM>, mds@hpcndaw.CND.HP.COM (Mark Smith) writes:
- |> Thanks to Bancroft Scott who sent me the following reply. I posted it
- |> in case anyone else was interested.
- |>
- |> Mark smith
- |>
- |>
- |> >I'm trying to understand section 24.6 of ISO/IEC 8824:1990 regarding
- |> >distinct identifiers.
- |> >
- |> >Given the following definitions:
- |> >
- |> >T1 ::= SEQUENCE { X1,
- |> > b BOOLEAN
- |> > }
- |> >
- |> >X1 ::= CHOICE { y INTEGER, z REAL }
- |> >
- |> >Would the identifiers for T1 be: y, z, b ??
- |>
- |> No. The only identifier for T1 is b, but y and z are visible to
- |> T1 because X1 does not have an identifier. In effect, this means
- |> that when creating a value reference, you will not be able to
- |> distinguish whether y and z were defined in T1 or in X1.
-
- I think you can distinguish whether y and z were defined in T1 or in X1
- because the value syntax of CHOICE type is different than that of SEQUENCE
- type. For example, t1 T1 ::= { y:123, b TRUE }
-
- ______________________________________________________________________________
- Tai Nguyen Email: ...!bae.bellcore.com!tain
- Bell Communication Research Phone: (908) 699-7934
- 444 Hoes Lane Room RRC 1B210
- Piscataway NJ, 08854
-