phil@shl.uucp (Phil Trubey) (10/17/90)
Does anyone know of any PD or commercial ASN.1 compilers that will run on a Sun SPARC? Thanks for any info... -- Phil Trubey (UUCP: ...!uunet!shl!phil)
baos@BACH.RUTGERS.EDU (10/30/90)
>Does anyone know of any PD or commercial ASN.1 compilers that >will run on a Sun SPARC? Open Systems Solutions, Inc. (609-987-9073) has developed a commercial ASN.1 compiler that runs under Sun OS (so Sun SPARC is supported), VAX/VMS, IBM MVS, AT&T System V Unix, Berkeley Unix, Apple Macintosh, MS-DOS, and several other operating systems. To the best of my knowledge, the OSS compiler is the most complete implementation of ASN.1 that is currently available on the market. The features of the product include: - support for the Type, Value, Subtype and Macro notations. All changes to ASN.1 are currently reflected in the compiler, including the October 1990 corrigenda. - support for circular references within and between ASN.1 modules. - supports ASN.1 as it is specified in ISO 8824 / CCITT X.208. No modifications are required to the abstract syntax (e.g., no need to remove the Value, Subtype or Macro notations). - highly descriptive messages - outstanding error recovery in the OSS ASN.1 Syntax Checker/Macro Expander, including synchronization on assignment statements (results in the detection of multiple errors in a single run of the compiler) and context sensitive spell checking of ASN.1 keywords. - assurance of tag uniqueness wherever required, such as at all levels of a CHOICE within a CHOICE within a CHOICE within a SET, etc. - choice of a table-driven (interpretive) encoder/decoder or a compiler- generated encoder/decoder. Both versions of the encoder/decoder employ the same interface, so that an application can switch from one to the other by simply recompiling. - comprehensive sanity checking in the decoder to guard against any invalid data that is presented for decoding. - choice of definite or indefinite length encoding. - optional trapping of signals in the encoder to recover from system-detected errors, such as bad pointers in the user data. - error message (optionally) returned by the encoder/decoder that details the cause of any error and identifies the field which was being encoded or decoded when the error was detected. - encoding (decoding) directly from (into) user's data structure; no intermediate steps used in encoding/decoding. Bancroft Scott