From: Detlef Vollmann <dv@vollmann.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot Developer's Information
Date: Wed, 17 Aug 2005 12:31:48 +0200 [thread overview]
Message-ID: <43031214.156E6D62@vollmann.ch> (raw)
In-Reply-To: 20050816215307.C793B352676@atlas.denx.de
Wolfgang Denk wrote:
>
> In message <200508160831.44688.bwaite@irobot.com> you wrote:
> >
> > a per-patch basis, We shoud remind ourselves that the // was adopted as a
> > legal C comment when C99 was ratified. The // style comment can arguably be
>
> Nevertheless many existing toolchains throw warning messages, and I
> see no reason to drop support of these older compilers.
My experience is just the other way around: the following
code throws an error for long long, but gives no warnings for //:
#define CFG_CMD_KGDB 0x00000200ULL // kgdb
#if (CFG_CMD_KGDB)
#define LONG_LONG_WORKS 1
#endif
Compiled with gcc version 2.95.2, and 'gcc -Wall -pedantic'
As this is an excerpt from u-boot, I'm a bit surprised about
your reasoning against '//'.
It might be pretty hard to find a toolchain that compiles
u-boot but throws a warning on '//'.
Detlef
--
Detlef Vollmann vollmann engineering gmbh
Linux and C++ for Embedded Systems http://www.vollmann.ch/
Linux for PXA270 Colibri module: www.toradex.com/e/products.html
prev parent reply other threads:[~2005-08-17 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 0:15 [U-Boot-Users] U-Boot Developer's Information Wolfgang Denk
2005-08-16 3:35 ` glikely at gmail.com
2005-08-16 7:29 ` Wolfgang Denk
2005-08-16 8:50 ` Richard Danter
2005-08-16 15:56 ` Wolfgang Denk
2005-08-16 10:00 ` [U-Boot-Users] " Catalin Marinas
2005-08-16 15:59 ` Wolfgang Denk
2005-08-16 16:22 ` Catalin Marinas
2005-08-16 12:31 ` [U-Boot-Users] " Brian Waite
2005-08-16 21:53 ` Wolfgang Denk
2005-08-17 10:31 ` Detlef Vollmann [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=43031214.156E6D62@vollmann.ch \
--to=dv@vollmann.ch \
--cc=u-boot@lists.denx.de \
/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