I am not a BNF expert, so just a layman's question: Can the problems
you are having be mended by simply changing the BNF in the ASN.1, or
would a mend affect the actual notation being defined?
If the former, do you have (or could you produce) a complete set of
proposed changes to the BNF that
Subject: Re: [ASN.1] asn specification
On Thu, 18 October 2001, Olivier Dubuisson wrote:
Andrew Sutton wrote:
hi,
i've gotten bored so i've been working on an ASN.1 compiler based on
the 97
specifications. actually, it was going pretty well until i realized
that i
had mistyped
On Thu, 25 Oct 2001, Ed Day wrote:
We have dealt with this problem and others like it using the infamous lex
tie-in that is prevalent in the SNACC code. That is to say swallow the
whole thing up and deal with it on the back end essentially emulating
multi-token look aheads. It isn't
Andrew Sutton wrote:
hi,
i've gotten bored so i've been working on an ASN.1 compiler based on the 97
specifications. actually, it was going pretty well until i realized that i
had mistyped the SymbolsImported productions. anyway, i ran into a problem
and had some feedback or could
