Can one access asn1ct's ASN.1 parser?

[Kenneth Lundin]

We have discussed to add functionality in the generated encoder (for the
maps variant) which checks that the map does not contain any "unknown"
keys, that is only allow keys which are corresponding to the names in the
ASN.1 spec. Probably this should be activated with a new compiler option
since it will probably have some negative impact on performance.

Is this what you need as well or are you thinking of some other solution
(or other problem)?

There is no API for the parse tree but there is an internal intermediate
format used by the backends.

/Kenneth, Erlang/OTP Ericsson


On Mon, Jan 4, 2021 at 11:44 AM Oliver Korpilla <oliver.korpilla@REDACTED>
wrote:

> Hello,
>
> is it possible to reuse the parsing part of asn1ct? Does it generate
> some intermediate structure?
>
> We have been using the "maps" instead of the "records" version of the
> generated codecs for a while. However, we found recently that we missed
> several instances of incompatible name changes because there's no name
> checking for the map members. Unknown map members just get omitted.
>
> I would like to investigate if I could add a layer for my project's use
> preventing that, but I have no desire to write another ASN.1 parser for
> that.
>
> Is there an API for accessing this information?
>
> Thank you,
> Oliver
>
>
> --
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20210104/60ca5489/attachment.htm>