diff options
| author | Björn Gustavsson <[email protected]> | 2013-06-27 14:49:12 +0200 |
|---|---|---|
| committer | Björn Gustavsson <[email protected]> | 2013-08-30 10:13:16 +0200 |
| commit | 9033435e5b8051608c7e867051c1a8e6b946d2a9 (patch) | |
| tree | 788ee5070999eb5d67b4c370175b71be2bc74d05 /bootstrap | |
| parent | bf13576de7f8a3cd56a268e3bf9cdf6535ea2334 (diff) | |
| download | otp-9033435e5b8051608c7e867051c1a8e6b946d2a9.tar.gz otp-9033435e5b8051608c7e867051c1a8e6b946d2a9.tar.bz2 otp-9033435e5b8051608c7e867051c1a8e6b946d2a9.zip | |
Remove broken support for multiple UNIQUE
According to the ASN.1 standard, having multiple UNIQUE in class
is allowed. For example:
C ::= CLASS {
&id1 INTEGER UNIQUE,
&id2 INTEGER UNIQUE
}
In practice, no one uses multiple UNIQUE.
The ASN.1 compiler will crash if a class with multiple UNIQUE
is used, but the backends have half-hearted support for multiple
UNIQUE in that they generate helper functions similar to:
getenc_OBJECT_SET(id1, 42) ->
fun enc_XXX/3;
...
Since we have no plans to implement support for multiple UNIQUE
(no one seems to have missed it), simplify the helper functions
like this:
getenc_OBJECT_SET(42) ->
fun enc_XXX/3;
...
Diffstat (limited to 'bootstrap')
0 files changed, 0 insertions, 0 deletions