You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only convention that differentiates triggering an event from calling a function now, is the capital letter at the beginning of an event.
I think it will be a better thing, to make the code of a Solidity snippet more clear, and make a developer's intentions explicit, is to prefer another naming convention for events such as:
Putting an "E_" at the beginning. Example: E_Transfer
Ending the name with "Event". Example: TransferEvent
Ending the name with "Log". Example: TransferLog
What do you think of this proposition?
The text was updated successfully, but these errors were encountered:
For code style conventions, the well-known ConsenSys Smart Contract Best Practices recommend adding a Log prefix. For language-level differentiation, please follow the discussion here: #2877
The only convention that differentiates triggering an event from calling a function now, is the capital letter at the beginning of an event.
I think it will be a better thing, to make the code of a Solidity snippet more clear, and make a developer's intentions explicit, is to prefer another naming convention for events such as:
What do you think of this proposition?
The text was updated successfully, but these errors were encountered: