Article View: comp.std.c
Article #3783Re: __FUNC__ vs __FUNCTION__
From: Paul Eggert
Date: Fri, 18 Aug 1995 22:17
Date: Fri, 18 Aug 1995 22:17
15 lines
1246 bytes
1246 bytes
h.b.furuseth@usit.uio.no (Hallvard B Furuseth) writes: >This feature should have a lowercase name. That would be fine with me -- I don't care about the name, I just care about the functionality. Another idea is to change the syntax to make it look more like a string constant in the first place, e.g. "\<function>". This would mean the function name could be part of a larger string without using string concatenation, e.g. "(\<function> exiting now...)". One possible advantage of the "\<function>" syntax is its backward compatibility: it would work with traditional C compilers without change, though it would just yield `<function>' instead of the function name.
Technical Details
Message-ID:
<4133ie$706@tattoo.twinsun.com>Path:
arc1-ca.pugleaf.net!in2.uu.net!twinsun!not-for-mailReferences:
<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> <HBF.95Aug18083732@durin.uio.no>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!in2.uu.net!twinsun!not-for-mail From: eggert@twinsun.com (Paul Eggert) Newsgroups: comp.std.c Subject: Re: __FUNC__ vs __FUNCTION__ Date: 18 Aug 1995 15:17:50 -0700 Organization: Twin Sun Inc, El Segundo, CA, USA Message-ID: <4133ie$706@tattoo.twinsun.com> 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> <HBF.95Aug18083732@durin.uio.no> NNTP-Posting-Host: tattoo.twinsun.com