This CR should also clarify what this individual string element is. We
have charstring and char, but not e.g. bitstring and bit.
In fact, we should go for a symmetric approach: either these individual
elements are supported on type level or they are strings with length 1.
This relates to our CR 183.
Cheers, Ina.
Anthony Wiles wrote:
> I agree with Stephan. I think we need a CR here.
>
> Regards,
> Anthony
>
>
>>
Original Message
>>From: Stephen TOBIES [This email address is being protected from spambots. You need JavaScript enabled to view it.]
>>Sent: 17 April 2003 10:10
>>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>>Subject: Re: accessing individual string elements
>>
>>
>>Hi Jacon,
>>
>>your observation is right - the static semantics comment in
>>the BNF would indeed rule out accessing individual string
>>elements for anything but bitstrings. Of course, this is not
>>intended, as the examples in the relevant sections of the
>>standard show. All string types should be accessible using
>>the index notation.
>>
>>BR
>>
>>Stephan
>>
>>
>>>
Original Message
>>>From: ext jacon wang [This email address is being protected from spambots. You need JavaScript enabled to view it.]
>>>Sent: 17. April 2003 02:25
>>>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>>>Subject: accessing individual string elements
>>>
>>>
>>>TTCN3
>>>
>>>refer to <<ETSI ES 201 873 v2.2.1>>
>>>In clause 6.1.2,It seems that all
>>>strings(bitstring,hexstring,octetstring,charstring,universal
>>>charstring) elements
>>>could be accessed using array-like syntax.
>>>But from TTCN3 BNF,it seems that only individual bitstring
>>>elements could be accessed using array-like syntax.
>>>(
>>>569. ExtendedFieldReference ::= {(Dot ( StructFieldIdentifier
>>>| ArrayOrBitRef | TypeDefIdentifier))
>>>| ArrayOrBitRef }+
>>>
>>>103. ArrayOrBitRef ::= "[" FieldOrBitNumber "]"
>>>/* STATIC SEMANTICS - ArrayRef shall be optionally used for
>>>array types and ASN.1 SET OF and
>>>SEQUENCE OF and TTCN record of and set of. The same notation
>>>can be used for a Bit reference inside
>>>an ASN.1 or TTCN bitstring type */
>>>)
>>>The static semantics above only denote that the same notation
>>>can be used for a Bit reference inside an ASN.1 or TTCN
>>>bitstring type.
>>>
>>>So I'm confused.
>>>Could you give me some advice?
>>>
>>>Thanks in advance.
>>>--
>>> Engineering is the art of making what you want from
>>>things you can get.
>>>
>>
>
--
Ina Schieferdecker
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241
