As recent release of solidity has been introduced 'emit' keyword to use with events to differentiate them from functions. This will be great if contracts of repository are updated so that they can be used with latest solidity compiler.
This upgrade will help to run the contract with latest solc compiler.
Seems like a reasonable task for an "update to 0.4.21" pull request, once 0.4.21 has been in the wild for a bit
The responsiveness to core updates reflects well on the community. Great work people.
On Mar 12, 2018, at 10:26 AM, Matt Condon notifications@github.com wrote:
Seems like a reasonable task for an "update to 0.4.21" pull request, once 0.4.21 has been in the wild for a bit
โ
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/OpenZeppelin/zeppelin-solidity/issues/807#issuecomment-372393771, or mute the thread https://github.com/notifications/unsubscribe-auth/Agl2IITa_TGcovSmJ27vPOVruUAYxQZeks5tdq_bgaJpZM4SlcBS.
@Shrugs do you have an ETA for this to be released? Thank you
Is this open?
It depends on what is expected from this PR (#863). Because it only fixes part of the compiler warnings from the new soidity compiler.
This can probably be closed with the improvements here https://github.com/OpenZeppelin/zeppelin-solidity/pull/876
thanks @icole! I had forgotten about this issue :)
when this fix will be released?
It will be published in version 1.9.0, currently scheduled for 1.5 weeks from now
how we can use this feature right now?
you can point your local project to the master branch of zeppelin-solidity
npm install git://github.com/OpenZeppelin/zeppelin-solidity.git#master --save
Why not bump minor version number for this? Warnings from a library are a silly thing, I'd love to get updates through npm proper... (adding master branch from git to package.json is obviously not wholly satisfactory since npm i might later break things). I'll just npm install git://github.com/OpenZeppelin/zeppelin-solidity.git#8f2a4785 --save-dev for now then.
aw shucks, that's no good, now I get the constructor() warnings. Hmmh.
constructor() warnings are due to the latest solidity version 0.4.22.
There were some bugs regarding constructor in 0.4.22, use 0.4.23
(and yes, I noticed there's fix/solidity-warns branch but I'm not going to add THAT to my package.json ๐ )