public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Vladimir Kondratiev <vladimir.kondratiev@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __FUNCTION__
Date: Tue, 8 Jan 2002 14:01:50 -0800	[thread overview]
Message-ID: <20020108220149.GA15816@kroah.com> (raw)
In-Reply-To: <3C3B664B.3060103@intel.com>
In-Reply-To: <3C3B664B.3060103@intel.com>

On Tue, Jan 08, 2002 at 11:36:11PM +0200, Vladimir Kondratiev wrote:
> Hello,
> Modern C standard (C99) defines __FUNCTION__ as if immediately after 
> function open brace string with function name is declared. Thus, it's 
> invalid to use string concatenations like __FILE__ ":" __FUNCTION__.

Hi,

Can you point me to the place in the spec this is defined?  I don't see
__FUNCTION__ defined anywhere in the ISO/IEC 9899:1999 (the official C99)
specification.

thanks,

greg k-h

  parent reply	other threads:[~2002-01-08 22:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 21:36 __FUNCTION__ Vladimir Kondratiev
2002-01-08 21:59 ` __FUNCTION__ Ian S. Nelson
2002-01-08 22:17   ` __FUNCTION__ Greg KH
2002-01-08 23:09   ` __FUNCTION__ Vladimir Kondratiev
2002-01-08 22:01 ` Greg KH [this message]
2002-01-08 22:56   ` __FUNCTION__ jtv
2002-01-08 23:11     ` __FUNCTION__ Greg KH
2002-01-08 23:39       ` __FUNCTION__ David Weinehall
2002-01-08 23:51         ` __FUNCTION__ Andrew Morton
2002-01-09  0:04           ` __FUNCTION__ David Weinehall
2002-01-09  0:14             ` __FUNCTION__ Andrew Morton
2002-01-09  0:23           ` __FUNCTION__ Anton Altaparmakov
2002-01-08 23:42       ` __FUNCTION__ jtv
2002-01-09  2:12       ` __FUNCTION__ Richard Henderson
2002-01-09  7:23         ` __FUNCTION__ Greg KH
2002-01-09  7:32           ` __FUNCTION__ Neil Booth
2002-01-09 22:35           ` __FUNCTION__ Richard Henderson
2002-01-09  9:05       ` __FUNCTION__ Martin Dalecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020108220149.GA15816@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vladimir.kondratiev@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox