From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: nickc@redhat.com
Cc: pierre.muller@ics-cnrs.unistra.fr, palves@redhat.com,
asmwarrior@gmail.com, gdb@sourceware.org,
binutils@sourceware.org
Subject: Re: [RFC-v2] BFD MinGW/Cygwin build error in bfd/peiXXgen.c
Date: Thu, 19 Dec 2013 13:02:00 -0000 [thread overview]
Message-ID: <201312191302.rBJD2UOJ010980@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <52B2E8C4.3080208@redhat.com> (message from nick clifton on Thu, 19 Dec 2013 12:38:28 +0000)
> Date: Thu, 19 Dec 2013 12:38:28 +0000
> From: nick clifton <nickc@redhat.com>
>
> > Another silly coding style question: Should there by a space
> > between the address operator "&" and the variable or expression following?
>
> *sigh* There is no strict rule on this subject. Most people omit the
> space, I include it. I feel that since we separate other operators from
> their arguments we should do the same with &. I feel the same way about
> the asterisk operator too, but not many people agree with me on that one
> either.
Spaces around binary operators, no spaces around unary operators.
That's pretty much the universally accepted standard, and the one used
by the official C standard.
Everybody who thinks differently has been poisoned by C++ ;).
next prev parent reply other threads:[~2013-12-19 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 9:54 GDB MinGW build error: implicit declaration of function 'wcsncasecmp' asmwarrior
2013-12-18 9:58 ` asmwarrior
2013-12-18 10:06 ` BFD " Pedro Alves
2013-12-18 12:50 ` asmwarrior
2013-12-18 15:47 ` Eli Zaretskii
2013-12-18 13:03 ` [RFC] BFD MinGW/Cygwin build error in bfd/peiXXgen.c Pierre Muller
2013-12-18 17:52 ` nick clifton
2013-12-19 11:45 ` [RFC-v2] " Pierre Muller
2013-12-19 12:41 ` nick clifton
2013-12-19 13:02 ` Mark Kettenis [this message]
2013-12-19 13:18 ` Pierre Muller
2013-12-19 15:13 ` nick clifton
[not found] ` <52b19d01.22cbc20a.69b0.ffffb29eSMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-18 13:25 ` [RFC] " asmwarrior
[not found] ` <52b19d19.0850420a.7b6a.52dcSMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-18 17:56 ` Pedro Alves
2013-12-19 11:15 ` nick clifton
2013-12-18 15:35 ` GDB MinGW build error: implicit declaration of function 'wcsncasecmp' Eli Zaretskii
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=201312191302.rBJD2UOJ010980@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=asmwarrior@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nickc@redhat.com \
--cc=palves@redhat.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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