Yoann Padioleau wrote: >>> >> Personal pet-peeve, use __func__, not __FUNCTION__. >> >> __func__ is C, __FUNCTION__ is a gcc-extension. > > Ok. Is there also a __file__, and __line__ ? If this > not the case then I would rather keep my __FUNCTION__, > it's estetically more consistent. > No, it's not. __FILE__ and __LINE__ are macros (handled by the preprocessor), but __func__ is a compiler token. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
