All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Zan Lynx <zlynx@acm.org>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>,
	ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH 33/39] reiserfs: split right balancing part of	balance_leaf() off
Date: Thu, 07 Jun 2007 21:28:55 -0400	[thread overview]
Message-ID: <4668B0D7.3050100@suse.com> (raw)
In-Reply-To: <1181257975.21257.9.camel@localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zan Lynx wrote:
> On Thu, 2007-06-07 at 18:01 -0400, Jeff Mahoney wrote:
>> Vladimir V. Saveliev wrote:
> [cut] 
>>> shouldn't function name prefixes be more consistent? Either bl_ or
>>> balance_leaf everywhere?
>>>
>> Yes, absolutely. Initially they were, but
>> balance_leaf_function_subfunction(parameter list) ended up with the
>> parameters grouped along the right margin. I wouldn't be opposed to
>> changing them all to bl_* except for balance_leaf itself.
> 
> Or you could trade vertical space for horizontal space and do like:
> 
> static void
> balance_leaf_right_paste_de_partial(
> 	struct tree_balance *tb, struct item_head *ih,
> 	const char *body, int flag, int *zeros_num,
> 	int item_pos, int *pos_in_item
> ) {
> 
> I always thought wasting all that horizontal space in parameter lists
> was silly just to save some vertical, and so many people get the
> tab-stop/space mix wrong.

Well, I actually meant with the call sites, where the start of the
funciton call is already two or three tab stops in. The next revision
uses bl_* for all of them.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGaLDXLPWxlyuTD7IRArMUAJ49r+82Hbj7TpHZOAIf3q1z3egV5ACeN+IH
iJroW0vmxIY1I6fiNDy/Dyg=
=p/e1
-----END PGP SIGNATURE-----

       reply	other threads:[~2007-06-08  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070530220511.681688471@mail.jeffreymahoney.com>
     [not found] ` <20070530222101.190219224@mail.jeffreymahoney.com>
     [not found]   ` <4668805C.2070408@namesys.com>
     [not found]     ` <46688053.4050409@suse.com>
     [not found]       ` <1181257975.21257.9.camel@localhost>
2007-06-08  1:28         ` Jeff Mahoney [this message]
     [not found] ` <46688C0C.2050102@namesys.com>
2007-06-08 16:02   ` [PATCH 00/39] reiserfs: patch queue Jeff Mahoney
     [not found] ` <20070530222058.368999370@mail.jeffreymahoney.com>
     [not found]   ` <46688BE3.2000807@namesys.com>
2007-06-08 18:59     ` [PATCH 07/39] reiserfs: introduce reiserfs_error() Jeff Mahoney

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=4668B0D7.3050100@suse.com \
    --to=jeffm@suse.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=vs@namesys.com \
    --cc=zlynx@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.