mitshell

This should now be fixed with: https://github.com/pycrate-org/pycrate/commit/1520fec7a427ae430138af59149b7de00d175bdc. If you confirm, I can re-tag a minor release.

In my recollection, these specs rely heavily on WITH COMPONENTS, which is not perfectly supported within pycrate. This will need some more investigation...

When trying to reproduce, I get a different error: ``` pycrate_asn1c.err.ASN1ProcTextErr: Ieee1609Dot2Data-Unsecured: missing mandatory components in WITH COMPONENTS ``` That means pycrate is not happy when the WITH COMPONENTS sub-select...

I don't have time currently to dive in the ASN.1 compiler code, so I'll keep this issue on hold unless someone volunteers to give it a try.

No move yet. Any PR on this will be much appreciated.

`set_val()`, `set_val_at()`, `get_val()` and `get_val_at()` are the methods to work on the values. Here, `get_at()` returns the sub-object, which has however no value, as an object's value always lives at...

You can select the parent value, and check which choice is taken as the 1st component of the value.

When we disable the bound constraints, as you do, we obtain the following value: ``` { callingDomainSelector '01'H, calledDomainSelector '01'H, upwardFlag TRUE, targetParameters { maxChannelIds 34, maxUserIds 2, maxTokenIds 0,...

Can't remember the good reason to return a `set` instead of a `list` (this was done 8 years ago), but I guess there was one. Looking at the code right...

I implemented the change in https://github.com/pycrate-org/pycrate/commit/91b7713c7a53a9b3c1ee2cf58dc5fc79a066a205. Let me know if this fits what you were expecting @dbressan2?