Lev Walkin

@kellerkindt Would you be willing to sign the CLA please?

@risicle, Regarding the CVE: Please see the history of this CVE here: https://github.com/vlm/asn1c/issues/190 Frankly I don't know how to deal with it properly. These bugs against _compilers_, not the _compiler's...

@mouse07410, thank you for all your efforts! I took a bit in already, but certainly the divergence is there and has to be dealt with. Lately I've been busy with...

@mouse07410, wrt co-maintainer: please sign the appropriate [CLA](http://lionet.info/asn1c/cla) and send the scanned PDF to my email.

The asn1c repository has the `.clang-format` file which standardizes the code style. I am reluctant to do a sweeping change in the whole codebase, as it will almost instantly provide...

Is there a way to support both bison 2 and bison 3?

Re workaround: such warnings are typically fixed by casting to void: `(void)param;` or by using `__attribute__((unused))` or the app-specific macro wrapping it, such as `GCC_UNUSED` for asn1c.

I cannot merge this, since the source codes should not contain binaries and since I can't allow myself be liable for potentially unverified third party executable code. Nothing personal, sorry....

I'll ask a few questions here. 1. What's the purpose of this change? if(expr->_anonymous_type) { - p = ASN_EXPR_TYPE2STR(expr->expr_type); - /\* warning: comparison is always false due to limited ra...

Also, the patch generates a regression: [vlm@nala:~/work/github/asn1c/tests (seantek-master)]> cat 23-bits-OK.asn1 | grep BS1 BS1 ::= BIT STRING { first(0), third(2), twenty-eight(v28) } one-zero-one BS1 ::= { first, third } --...