From: Christopher Michael <cpmichael1@co...> - 2010-08-02 21:50:59
On 08/02/2010 05:46 PM, Iván Briano (Sachiel) wrote:
> On Mon, Aug 2, 2010 at 6:43 PM, Christopher Michael
> <cpmichael1@...> wrote:
>> On 08/02/2010 05:19 PM, Gustavo Sverzut Barbieri wrote:
>>> On Mon, Aug 2, 2010 at 4:06 PM, Enlightenment SVN
>>> <no-reply@...> wrote:
>>>> Rename 'same named' macros.
>>>> NB - Please use different macro names in the future for stuff like this
>>>> (ie: not the same macro name in each file) as it spits nasty compiler
>>>> warnings when compiling w/ amalgamation.
>>> no, if you do such local macros, undef them after you're done with it.
>>> Usually the purpose of the macro is to type less and adding a prefix
>>> does not help :-P
>> Well, yea, undef is cool too :) (not sure how that will affect
>> amalgamation tho as both macros would still have the same name in this
> Once #undef`ed, it ceases to exist. You can #define it again later
> and should not give any problems.
Ok, well either way doesn't matter to me ;) I just hate seeing compiler
warnings for something that is pretty simple to avoid if people just
took an extra 5 seconds to either use a different name, or undef them :)
Get latest updates about Open Source Projects, Conferences and News.