Conversation
|
This is actually a compile error, not a type. Also fixed in #21 |
|
@peecky : Any update? |
|
I have seen there is little progress on this project over the past few years. My project, the net-snmp project, depends on this project, so I have cloned it and migrated (i.e. copied) all the outstanding issues and pull requests. I will be releasing a new version of my version of this project under the asn1-ber namespace on npmjs.org by the end of the week which should address this particular item (I've already pushed the current code to this namespace to reserve it). I am now tracking all changes under my own copy at asn1-ber. Note that this is not a "fork" but a clone and fresh commit to a new repository. I have of course retained all copyrights and attributed back the original author. There are quite a few projects dependant on this project, and I want to make sure there is momentum on the issues and feature requests reported. |
|
This issue has been addressed in my version of this project which has now been published to npm: |
I found a meaningless if condition which always become false, because not operator(
!) is evaluated before theinstanceofoperator.