...00 05 0c 00 33and for 0.6.0 of course
..00 06 00 00 33. It differs on several other bytes, but that should be the hashed contract metadata that has a different version number in it.
solc-js. We could easily move them to Solidity's compilation tests. The question is, can the current contracts in solc-js be language independent? AFAICT, it's mostly about bytecode comparison and as you said, bindings
The question is, can the current contracts in solc-js be language independent?
The only thing the bindings need to tests are:
These can be written in a way that they would hardly require syntax updates (but definitely not to the extent the DAO could/would in the future).
These can be written in a way that they would hardly require syntax updates
Yea this would be nice. A bunch of one line contracts that test all the bindings
master_060branch in solc-js. For now, I updated the solc version switch with https://github.com/ethereum/solc-js/pull/383/, which should also work with older compilers. Right now, I don't see a particular reason to have that separated.