On 08/02/2010 05:46 PM, Iván Briano (Sachiel) wrote:
> On Mon, Aug 2, 2010 at 6:43 PM, Christopher Michael
> <cpmicha...@comcast.net>  wrote:
>> On 08/02/2010 05:19 PM, Gustavo Sverzut Barbieri wrote:
>>> On Mon, Aug 2, 2010 at 4:06 PM, Enlightenment SVN
>>> <no-re...@enlightenment.org>    wrote:
>>>> Log:
>>>>    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
>> case).
>>
>
> 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 :)

dh

>> dh
>>
>>

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to