Does the current eSNACC compiler support parameterised types and information object classes?

["David Lowndes" <David.Lowndes@xxxxxxxxxxxxxxx>]

Title: Does the current eSNACC compiler support parameterised types and information object classes?

I'm trying to compile the set of ASN.1 sources for X.420 1999 and get errors like this:

IPMSInformationObjects.asn(32) : parse error at symbol "{"

IPMSInformationObjects.asn(108) : parse error at symbol "EXTENSION"

&&@&&&&&&&&&&
Parsing errors---cannot proceed

Line 32 seems to be an indicator for a parameterised type "content-body-part{}":

IMPORTS
  content-body-part{}
    FROM IPMSForwardedContentBodyPartType {joint-iso-itu-t mhs(6) ipms(1)
      modules(0) forwarded-content-body-part-type(15)}

And line 108 is:

IPMPerRecipientEnvelopeExtensions EXTENSION ::=
  {blind-copy-recipients | body-part-encryption-token |
   forwarded-content-token, ...}

Which is defined (and exported) from another module as:

EXTENSION ::= CLASS {
  &id           ExtensionType UNIQUE,
  &Type         OPTIONAL,
  &absent       &Type OPTIONAL,
  &recommended  Criticality DEFAULT {}
}
WITH SYNTAX {
  [&Type
   [IF ABSENT &absent],]
  [RECOMMENDED CRITICALITY &recommended,]
  IDENTIFIED BY &id
}

The OSS C++ compiler doesn't have any similar problems with these same sources.

Regards
David Lowndes