🚀 go-pugleaf

In article <1995Jul25.180413.3420@news.wrc.xerox.com> leisner@sdsp.mc.xerox.com (Marty Leisner 25733) writes:
> I lobbied for __FUNC__ for years...Aztec C had a __FUNC__ which
> was incredibly useful...

BTW, I compared gcc's __FUNCTION__ with the __func proposal at the ISO C
site (ftp://ftp.dmk.com/DMK/sc22wg14/c9x/func/func.txt.gz), and I'd
suggest to copy __FUNCTION__ instead of that from the proposal.

* __FUNCTION__ is actually a string, so we can use string concatenation:
	void foo () { puts ( "Called " __FUNCTION__ "()."); }
  and so it also ends up in read-only memory, like real strings, despite
  its non-const* type.  While the __func proposal suggests
	static char __func[] = "name";
  to get correct type and correct sizeof(__func).

* __FUNCTION__ is defined outside functions (as ""), so macros can
  safely use it without worrying about how and where they are called.

-- 
Regards,

Hallvard