public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Brian Waite <bwaite@irobot.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot Developer's Information
Date: Tue, 16 Aug 2005 08:31:44 -0400	[thread overview]
Message-ID: <200508160831.44688.bwaite@irobot.com> (raw)
In-Reply-To: <20050816001516.11FBA353CEB@atlas.denx.de>

On Monday 15 August 2005 8:15 pm, Wolfgang Denk wrote:

>
>     Please note that U-Boot is implemented in C (and to some small
>     parts in Assembler); no C++ is used, so please do not use C++
>     style comments (//) in your code.
>
Only to be contririan, and to get the debate out of the way now instead of on 
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 
called a C style comment by people who graduated college after me. If you 
really don't like the // comment ( I know I don't) I think a little more 
verbage might be in order explicitly forbidding the // comment on the grounds 
of u-boot being developed under the C89 specification, or just an outright 
don't do it. Otherwise people will argue this on each patch they develop. 
You've seen it on LKML so lets make this a bit more clear.


Thanks 
Brian

  parent reply	other threads:[~2005-08-16 12: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 ` Brian Waite [this message]
2005-08-16 21:53   ` [U-Boot-Users] " Wolfgang Denk
2005-08-17 10:31     ` Detlef Vollmann

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=200508160831.44688.bwaite@irobot.com \
    --to=bwaite@irobot.com \
    --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