-
Notifications
You must be signed in to change notification settings - Fork 574
Change annotations to match the standardese style #426
base: develop
Are you sure you want to change the base?
Conversation
… documentation and the md file explaining how to do it.
*/ | ||
[[eosio::action]] | ||
void exec( ignore<name> executer, ignore<transaction> trx ); | ||
[[eosio::action]] void exec( ignore<name> executer, ignore<transaction> trx ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
N.B. this type of change is a must, otherwise standardese chokes with a critical error and aborts its execution, that is, the [[eosio::action]]
has to be on the same line with the function declaration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@larryk85 Does this cause issues? There is no way around this requirement when using Standardese. When the C++ style declarations are multi-line Standardese does not find the entity.
It could be possible to fix this, but not sure if we have the resources. Are multi-line declaration/entity signatures a compiler requirement?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are not a compiler requirement, the attributes are only lexically linked to the first binding token. So you can place them on the same line or 100 lines between them, the compiler doesn't care. That is odd that standardese would fail on that, it should be using Clang to parse the code and working off of the AST that it generates. I would've expected it to fail in both cases then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change Description
Change annotations to be Standardese compatible.
Resolves #392
Deployment Changes
API Changes
Documentation Additions
Notes