public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Nathan ." <snmptoddler@hotmail.com>
To: gcc@gcc.gnu.org
Subject: expalin this syntax pls
Date: Thu, 17 Oct 2002 23:32:00 -0000	[thread overview]
Message-ID: <F178ZKxsu9cEpSWdHqS00001c4e@hotmail.com> (raw)

Hello All,

Is it correct to leave a space in declaring args to following function. This 
has been cut paste from  file  /usr/include/netdb.h.
Quite surprisingly there is no compilation error but please explain me this 
novel syntax. All these lines have a space ..looks a space if not some 
invisible character. plz expalin this anomally. e.g there is a space between 
__restrict and __name ..

======= from /usr/include/netdb.h ===================
extern int gethostbyname_r (__const char *__restrict __name,   <<<<see this 
line
                            struct hostent *__restrict __result_buf,        
<<<<see this line
                            char *__restrict __buf, size_t __buflen,
                            struct hostent **__restrict __result,            
  <<<<see this line
                            int *__restrict __h_errnop) __THROW;

==================================================


Thanks for ur patience
Please Advise,
-Nitin








_________________________________________________________________
Get faster connections -- switch to MSN Internet Access! 
http://resourcecenter.msn.com/access/plans/default.asp

             reply	other threads:[~2002-10-18  0:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 23:32 Nathan . [this message]
2002-10-18  4:23 ` Jim Wilson
2002-10-18 14:27   ` restrict keyword [was: expalin this syntax pls] Joe Buck
2002-10-18 18:46     ` Joseph S. Myers
2002-10-18 21:53       ` Joe Buck
2002-10-18 21:55         ` Joseph S. Myers
2002-10-18 23:07     ` kwall

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=F178ZKxsu9cEpSWdHqS00001c4e@hotmail.com \
    --to=snmptoddler@hotmail.com \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).