> Hi Krishna,
> It will not affect Unaligned or for that matter Aligned PER in any way.
> So the encoding for MyCHOICE_1 and MyCHOICE_2 will be same.
> Same will be true for MySEQUENCE_1 and MySEQUENCE_2.
It is best if off-the-shelf tools were used so that major errors such as
this are avoided in implementing applications that use PER. Such errors
and many others stemming from implementors not closely reading the docs
or available books can be a nasty source of interoperability problems.
The cost in recovering from such easily avoidable problems often far
outweigh the savings derived from writing encoders/decoders by hand.
You are mistaken. See X.680 clause 24.2. The encoding of MyCHOICE-1
and MyCHOICE-2 are different because MyCHOICE-1 contains a tagged
alternative (actually, two), which results in automatic tagging not
being in effect for this choice type.
--
Olivier DUBUISSON
france telecom R&D
_ DTL/MSV - 22307 Lannion Cedex - France
( ) tel: +33 2 96 05 38 50 - fax: +33 2 96 05 39 45
/.\/ --------------------------------------
\_/\ Site ASN.1 : http://asn1.elibel.tm.fr/
