-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Solidity compiler version missing #534
Comments
Hi @karalabe, how exactly would be the best way to display Solidity version? Only a small text around the editor would suffice? Or embed this information alongside with the contract, in some way? |
@evertonfraga I guess while the former is be the way to go, embedding it in some standardized way would be required. Is there some EIP on this? Is there a meta-data section within contracts? To accomplish the former we might want to use the compiler version key-value pair from the resulting var testSource='contract Test { function double(int a) constant returns(int) { return 2*a; } }'
var testCompiled = web3.eth.compile.solidity(testSource);
console.log(testCompiled) { Test:
{ code: '0x6060604052602a8060106000396000f3606060405260e060020a60003504636ffa1caa8114601a575b005b6002600435026060908152602090f3',
info:
{ source: 'contract Test { function double(int a) constant returns(int) { return 2*a; } }',
language: 'Solidity',
languageVersion: '0.3.6',
compilerVersion: '0.3.6',
compilerOptions: '--bin --abi --userdoc --devdoc --add-std --optimize -o /var/folders/1r/vtmg53tn17g9m35zd64lyczh0000gn/T/solc777625456',
abiDefinition: [Object],
userDoc: [Object],
developerDoc: [Object] } } } |
This might be obsolete due to solidity's version-pragma requirement. |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
One of the most important features is the ability to verify deployed contracts. However mist does not display the Solidity compiler version it uses to deploy a contract, so afterwards it's extremely hard to guess which version it was and have the contract verified by block explorers. I think we should definitely have the version number displayed when working with solidity code directly.
The text was updated successfully, but these errors were encountered: