Article View: comp.std.c
Article #3774Re: __FUNC__ vs __FUNCTION__
From: Hallvard B Furuseth
Date: Fri, 18 Aug 1995 06:37
Date: Fri, 18 Aug 1995 06:37
18 lines
1272 bytes
1272 bytes
eggert@twinsun.com (Paul Eggert) writes: >dmm@neutron.torolab.ibm.com (Dave Mooney) writes: >>I agree that this is the most useful design for __FUNC__, but it is >>unfortunately quite incompatible with the phases-of-translation model in >>the Standard. Macros are expanded in translation phase 4, string literals >>get pasted in phase 6, but the implementation doesn't know what function it >>is translating until phase 7. > > But __FUNCTION__ is not a macro; it is a special construct that is > equivalent to a string constant. Yes. No. Everyone "knows" that uppercase names denote macros. This feature should have a lowercase name. -- Regards, Hallvard
Technical Details
Message-ID:
<HBF.95Aug18083732@durin.uio.no>Path:
arc1-ca.pugleaf.net!nntp.uio.no!usenetReferences:
<3udssr$32j@info1.sdrc.com> <3uu5an$ohi@info1.sdrc.com> <1995Jul25.180413.3420@news.wrc.xerox.com> <HBF.95Aug1194442@durin.uio.no> <40t0k3$pom@tornews.torolab.ibm.com> <40t7k0$3r4@light.twinsun.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!nntp.uio.no!usenet From: h.b.furuseth@usit.uio.no (Hallvard B Furuseth) Newsgroups: comp.std.c Subject: Re: __FUNC__ vs __FUNCTION__ Date: 18 Aug 1995 06:37:34 GMT Organization: University of Oslo, Norway Message-ID: <HBF.95Aug18083732@durin.uio.no> References: <3udssr$32j@info1.sdrc.com> <3uu5an$ohi@info1.sdrc.com> <1995Jul25.180413.3420@news.wrc.xerox.com> <HBF.95Aug1194442@durin.uio.no> <40t0k3$pom@tornews.torolab.ibm.com> <40t7k0$3r4@light.twinsun.com> NNTP-Posting-Host: durin.uio.no In-reply-to: eggert@twinsun.com's message of 16 Aug 1995 09:50:08 -0700