On Tue, Jan 08, 2002 at 03:11:47PM -0800, Greg KH wrote: > > Any reason _why_ they would want to break tons of existing code in this > manner? Just the fact that the __func__ symbol is there to use? At a guess, it probably gives the gcc folks some more leeway as to where they implement the feature relative to string constant concatenation and such. If that is indeed the case, it could lead to cleaner code. > Since the C99 spec does not state anything about __FUNCTION__, changing > it from the current behavior does not seem like a wise thing to do. I'm pretty sure it's got to be in there somewhere--it was in the summary I read at the time. :) Jeroen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- __FUNCTION__Vladimir Kondratiev <vladimir.kondratiev _at_ intel.com>
- Re: __FUNCTION__Greg KH <greg _at_ kroah.com>
- Re: __FUNCTION__jtv <jtv _at_ xs4all.nl>
- Re: __FUNCTION__Greg KH <greg _at_ kroah.com>
- Prev by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by Date: Re: Two hdds on one channel - why so slow?
- Previous by thread: Re: __FUNCTION__
- Next by thread: Re: __FUNCTION__
- Indexes:[Main][Thread]