From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <4CE5DB8A.2010507@gmail.com> References: <4CE4B9DA.2060906@gmail.com> <4CE5DB8A.2010507@gmail.com> Date: Fri, 19 Nov 2010 00:13:01 -0300 Message-ID: From: "Federico G. Benavento" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Plan9 development Topicbox-Message-UUID: 85805ec6-ead6-11e9-9d60-3106f5b1d025 my bad, I thought cpp(1) implemented __FUNCTION__... On Thu, Nov 18, 2010 at 11:06 PM, Joel C. Salomon wrote: > On 11/18/2010 05:50 PM, Federico G. Benavento wrote: >> On Thu, Nov 18, 2010 at 2:30 AM, Joel C. Salomon wrote: >>> Why is __func__ listed as =E2=80=9Cunwanted=E2=80=9D? =C2=A0I=E2=80=99v= e found it useful for some >>> logging functions. >>> >> isn't this redundant with cpp(1)'s __FUNCTION__? >> >> if __FUNCTION__ isn't standard, then we should change >> it to __func__ in cpp and that's it > > Um, how can the preprocessor know what function it=E2=80=99s in middle of= ? > > (That=E2=80=99s why, unlike the preprocessor symbols __FILE__ & __LINE__,= C99=E2=80=99s > __func__ is an identifier.) > > --Joel > > --=20 Federico G. Benavento