Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crowdsale not compiling: problem with GoalReached #3018

Closed
wrisx opened this issue Oct 3, 2017 · 4 comments
Closed

Crowdsale not compiling: problem with GoalReached #3018

wrisx opened this issue Oct 3, 2017 · 4 comments

Comments

@wrisx
Copy link

wrisx commented Oct 3, 2017

System information

Geth version: geth version 1.7.0
OS & Version: Windows 10

Expected behaviour

Deploy the crowdsale contract in the Ethereum wallet. The code from: https://www.ethereum.org/crowdsale. The code is pragma solidity ^0.4.16.

Actual behaviour

It won't. It says: Could not compile source code. And then the error stated below this text. Does anybody know how to still deploy a crowdsale?

Backtrace

Could not compile source code.

This declaration shadows an existing declaration.
event GoalReached(address beneficiary, uint amountRaised);
^-----------------^

@axic
Copy link
Member

axic commented Oct 3, 2017

Unfortunately this is a bug in Mist (Ethereum wallet). This is a warning and not an error. It has been raised at Mist before: ethereum/mist#2797

You can compile the contract with Remix (https://remix.ethereum.org) or try renaming GoalReached to not conflict with another declaration.

@chka
Copy link

chka commented Oct 20, 2017

ehh... it's not a bug, it simply needs different variables inside the event:

event GoalReached(address beneficiary1, uint amountRaised1);

@axic
Copy link
Member

axic commented Oct 21, 2017

The bug in Mist is that it considers Solidity warnings as errors (without a way to disable this behaviour) and shadowing declarations is only a warning.

@acgoldfish
Copy link

The Bug in Mist is these Warnings are been treated as a hard Errors
ethereum/mist#2797 when is this going to be fixed ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants