aboutsummaryrefslogtreecommitdiffstats
path: root/lib/asn1/test/asn1_app_test.erl
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2014-10-13 15:59:27 +0200
committerBjörn Gustavsson <[email protected]>2015-01-12 11:40:24 +0100
commit8e43bffda5069aecdd2375eb409e9c03b7ff692b (patch)
treee4728d73b01d4f40d32a7048c7c8185857105074 /lib/asn1/test/asn1_app_test.erl
parent56ab55449e38de8b28df5e2b7e3e6bbebfecd1ba (diff)
downloadotp-8e43bffda5069aecdd2375eb409e9c03b7ff692b.tar.gz
otp-8e43bffda5069aecdd2375eb409e9c03b7ff692b.tar.bz2
otp-8e43bffda5069aecdd2375eb409e9c03b7ff692b.zip
Simplify handling of an empty object definition
When the parser sees: something SOMETHING ::= {} it has no way of knowing whether 'something' is an value or an object. It depends on how SOMETHING is defined. For example: SOMETHING ::= SEQUENCE {} or SOMETHING ::= CLASS { &id OPTIONAL } Because of that ambiguity, there is no way to avoid a special case when we check an object definition. However, there is no need to invent an entire new checking function for this special case. It is much easier to just pretend that the parser gave us {object,defaultsyntax,[]} and let check_objectdefn/3 check it in the usual way.
Diffstat (limited to 'lib/asn1/test/asn1_app_test.erl')
0 files changed, 0 insertions, 0 deletions