linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn@gclements.plus.com>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: linux prg <linux-c-programming@vger.kernel.org>
Subject: Re: __asm__
Date: Sat, 2 Apr 2005 14:18:45 +0100	[thread overview]
Message-ID: <16974.39861.142816.892982@gargle.gargle.HOWL> (raw)
In-Reply-To: <20050329064829.52787.qmail@web52908.mail.yahoo.com>


Ankit Jain wrote:

> can anybody tell me when we write like this while
> writing asm construct then what does underscore mean?
> 
> __asm__("construct")

Underscores are treated just like letters in macro and symbol names.

By convention, the implementation (compiler, core libraries) puts
underscores at the beginning of any "private" names, so that they
don't conflict with any names which you might use in your code (you
wouldn't normally choose names beginning with underscores in your own
code).

According to the ANSI C99 specification:

       7.1.3  Reserved identifiers

       [#1] Each header declares or defines all identifiers  listed
       in  its  associated  subclause,  and  optionally declares or
       defines identifiers listed in its associated future  library
       directions   subclause  and  identifiers  which  are  always
       reserved either for  any  use  or  for  use  as  file  scope
       identifiers.

         -- All  identifiers  that  begin  with  an  underscore and
            either an uppercase letter or  another  underscore  are
            always reserved for any use.

         -- All  identifiers  that  begin  with  an  underscore are
            always reserved for use as identifiers with file  scope
            in both the ordinary and tag name spaces.

-- 
Glynn Clements <glynn@gclements.plus.com>

      parent reply	other threads:[~2005-04-02 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29  6:48 __asm__ Ankit Jain
2005-03-29  7:40 ` __asm__ Steve Graegert
2005-04-02 13:18 ` Glynn Clements [this message]

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=16974.39861.142816.892982@gargle.gargle.HOWL \
    --to=glynn@gclements.plus.com \
    --cc=ankitjain1580@yahoo.com \
    --cc=linux-c-programming@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).