From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] /* inside comment in libfdt.h
Date: Thu, 03 Jan 2008 13:28:06 -0600 [thread overview]
Message-ID: <1199388486.15929.24.camel@ld0161-tx32> (raw)
In-Reply-To: <477B8DE6.5060501@ge.com>
On Wed, 2008-01-02 at 07:13, Jerry Van Baren wrote:
> Yes, nested comments is something that should not be done and should be
> fixed. This was inherited from the original code, although the current
> version uses // for the embedded comment which avoids the issue (but
> causes "no C++ comments" people to break out in rashes).
>
> <http://jdl.com/git_repos/?p=dtc.git;a=blob;f=libfdt/libfdt.h;h=ac0f5c3d1b41a1f6a8a5637a11d3ae4b9b6e6ed4;hb=3e516d961a45a2a410a9dc8f61fbdd62641b5ca0#l547>
Woah, hey! That's me!
Uh...
> Hmm, interesting, the original appears to have always used //, so it
> would appear that we (u-booties) did the change to /* */.
> <http://jdl.com/git_repos/?p=dtc.git;a=commitdiff;h=53acf491e9d576519f97b62984762498f9453cb4>
> I'll have to look at this further.
>
> My inclination is to change to embedded // comments to avoid drifting
> from the original due to aesthetics rather than due to necessary
> functionality differences.
>
> The alternative would be to convince David Gibson (/jdl) to adopt the
> ...other code here... change. I prefer the ... change if it matters -
> if somebody blindly cuts and pastes the example code, it won't compile
> until he understands and edits what he pasted.
Oh man....
OK. For the record, I'm all for only comments like this:
/*
*
*/
Clearly lax, I'll start enforcing it on the DTC sources more.
Sorry.
jdl
next prev parent reply other threads:[~2008-01-03 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 12:46 [U-Boot-Users] /* inside comment in libfdt.h Matthias Fuchs
2008-01-02 13:13 ` Jerry Van Baren
2008-01-02 13:49 ` Matthias Fuchs
2008-01-03 19:28 ` Jon Loeliger [this message]
2008-01-03 19:35 ` Scott Wood
2008-01-03 19:47 ` Jerry Van Baren
2008-01-03 23:41 ` David Gibson
2008-01-04 10:24 ` Matthias Fuchs
2008-01-04 12:43 ` Jerry Van Baren
2008-01-04 16:22 ` Jon Loeliger
2008-01-02 15:01 ` Wolfgang Denk
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=1199388486.15929.24.camel@ld0161-tx32 \
--to=jdl@freescale.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