Linux IA64 platform development
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] 80-column reformatting for fsys.S
Date: Fri, 25 Aug 2006 08:46:33 +0000	[thread overview]
Message-ID: <20060825084633.B86553404A@koto.vergenet.net> (raw)
In-Reply-To: <1156288081.7332.15.camel@fcboson.fc.hp.com>

On Thu, 24 Aug 2006 18:15:29 +0000, Al Stone wrote:
> On Thu, 2006-08-24 at 09:09 -0700, Luck, Tony wrote:
>> > > Could you convert the C++ comments to C comments while you are at it?
>> >
>> > Good idea.  I'll try to make a second pass on the ones I've done,
>> > and make it a point to do it in the future.
>> 
>> I'm not so sure that this is such a great idea ... using C comments will
>> trim another 2 or three characters off the space you have available
>> on each line (depending on whether you like /*comment*/ or /* comment */)
>> so you will either need to be more terse in order to fit, or have more
>> comments run onto two lines, neither of which sound like an improvememt
>> to maintainability).
> 
> I'm not personally committed to either style of comment.  I agree
> that it could compress things in a bad way to use C-style.  And I'm
> not really that particular that they all need to be one style or the
> other (both seem to be used intermittently within the same file).
> I'll gladly bow to the majority, whichever it is.
> 
>> The 80-column rule has considerable merit (I like to have two code
>> windows side-by-side, and my employer has shown no signs of wanting
>> to shell out for a 24+" monitor for me :-( ... but I'm really not
>> so sure why people are so anti-c++ comments {BTW, I don't see this
>> prohibition in Documentation/CodingStyle ... is this just another
>> unwritten rule that everyone knows about?)
> 
> Heh.  Indeed.  As my eyes get older, the monitors seem to have to get
> larger :).  And hence the 80-column cleanup.
> 
> I couldn't find comment _style_ mentioned in CodingStyle either.  The
> only reason I know of for using C-style comments is to maintain some
> consistency with C; logically, that makes _some_ sense, but again, I
> personally don't care that much one way or the other.  I'm willing
> to go with whatever gets accepted as a patch :).

I don't really like them much myself, but that is beside the point.
I thought it was in the style guide, but if its not, I have no problem
with them staying there.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


      parent reply	other threads:[~2006-08-25  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 23:08 [PATCH] 80-column reformatting for fsys.S Al Stone
2006-08-24  2:17 ` Al Stone
2006-08-24  2:36 ` Horms
2006-08-24 16:09 ` Luck, Tony
2006-08-24 18:15 ` Al Stone
2006-08-25  8:46 ` Horms [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=20060825084633.B86553404A@koto.vergenet.net \
    --to=horms@verge.net.au \
    --cc=linux-ia64@vger.kernel.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