mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Ram Pai <linuxram@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Miklos Szeredi <miklos@szeredi.hu>,
	mike@waychison.com, bfields@fieldses.org, serue@us.ibm.com
Subject: Re: [RFC PATCH 1/10] vfs: Lindentified namespace.c
Date: Sat, 17 Sep 2005 15:33:00 +0200	[thread overview]
Message-ID: <20050917133300.GA12369@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20050917123457.GJ19626@ftp.linux.org.uk>

On Sat, 17 September 2005 13:34:57 +0100, Al Viro wrote:
> On Sat, Sep 17, 2005 at 02:18:48PM +0200, J?rn Engel wrote:
> > 
> > It is an approximation.  In my personal experience, the "-l80"
> > parameter is doing a lot of harm.  It causes things like
> > 
> > 	if (...)
> > 		for (...)
> > 			while (...)
> > 				if (...)
> > 					for (...)
> > 						while (...)
> > 							some_function(argument,
> > 									very_long_argument,
> > 									another_argument,
> > 									0,
> > 									1,
> > 									NULL
> > 									);
> 
> ... show up as unreadable crap they are.  I fail to see a problem...
> Fix them and run Lindent again, that's it.

Without -l80, this crap takes up fewer lines.  Such things usually
occur in 500+ line functions, not counting Lindent expansion.  Getting
a fair amount of those lines on the screen helps when fixing things
up.

But that's just my personal approach.  As long as the results are
sane, it doesn't really matter.

> Lindent behaviour wrt labels is far more annoying, ditto for the mess it
> often makes out of prototypes (demonstrated in the patch in question).
> 
> IME the best way to use Lindent is to do vi -c 's/[[:space:]]*$//|x' foo.c
> first, then run Lindent, then walk through prototypes and fix them,
> diff with pre-Lindent version and see if it looks sane...

You're lucky.  I've had to deal with code where the diff with
pre-Lindent version was completely pointless.  Original was so broken,
there was no room for regressions.

Jörn

-- 
"Error protection by error detection and correction."
-- from a university class

      reply	other threads:[~2005-09-17 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 18:26 Ram
2005-09-16 18:51 ` Alexey Dobriyan
2005-09-16 20:55 ` Benjamin LaHaise
2005-09-16 21:29   ` Ram Pai
2005-09-16 21:25 ` Andrew Morton
2005-09-16 21:38   ` Matthew Wilcox
2005-09-16 21:39   ` Ram Pai
2005-09-17 12:18     ` Jörn Engel
2005-09-17 12:34       ` Al Viro
2005-09-17 13:33         ` Jörn Engel [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=20050917133300.GA12369@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=akpm@osdl.org \
    --cc=bfields@fieldses.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=mike@waychison.com \
    --cc=miklos@szeredi.hu \
    --cc=serue@us.ibm.com \
    --cc=viro@ftp.linux.org.uk \
    /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

all inboxes | Powered by JetHome®