-
Notifications
You must be signed in to change notification settings - Fork 3
[Evil] EAPI -> EVIL_API #169
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
[Evil] EAPI -> EVIL_API #169
Conversation
JPTIZ
left a comment
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.
Seems fine.
|
Tem como fazer um squash antes de mergear/rebase/cherry-pick ? Não faz sentido ficar com 2 commits |
Sim, a gente tem usado squash and merge . |
src/lib/evil/evil_api.h
Outdated
| #ifdef EVIL_API | ||
| #undef EVIL_API |
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.
If EVIL_API is already defined shouldn't it yield an error? As it shouldn't be already defined?
Coquinho
left a comment
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.
Shouldn't this evil_api.h use EVIL_STATIC and EVIL_BUiLD?
Yeah, you're right, I'll change it to work in the same way of the other APIs. |
d149536 to
0cffb19
Compare
| #ifdef EVIL_API | ||
| #error EVIL_API should not be already defined | ||
| #endif |
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.
If we're using evil_api.h, there's no reason to check this at all actually, since the include-guards will handle it.
* Renaming EAPI to EVIL_API * Modified to use EVIL_BUILD
* Renaming EAPI to EVIL_API * Modified to use EVIL_BUILD
No description provided.