From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: {PATCH} isofs stuff
Date: Thu, 23 Nov 2000 22:59:00 +0200 [thread overview]
Message-ID: <20001123225900.E28963@mea-ext.zmailer.org> (raw)
In-Reply-To: <20001123205731.A26914@gruyere.muc.suse.de> <Pine.LNX.4.10.10011231235170.1338-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10011231235170.1338-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Thu, Nov 23, 2000 at 12:38:55PM -0800
On Thu, Nov 23, 2000 at 12:38:55PM -0800, Linus Torvalds wrote:
...
> In fact, almost all filesystems do this at some point. ext2 does it for
> directories too, for some very similar reasons that isofs does. See
> fs/ext2/dir.c:
>
> blk = (filp->f_pos) >> EXT2_BLOCK_SIZE_BITS(sb);
>
> (and don't ask me about the extraneous parenthesis. I bet some LISP
> programmer felt alone and decided to make it a bit more homey).
>
> Linus
Propably some programmer has been bitten once too many times with
C's operator precedence rules, which only affect more complicated
expressions -- and thus are used rarely, and not remembered well.
(Or perhaps rememberance is felt to be weak, and parenthesis solve it.)
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 3:50 Andries.Brouwer
2000-11-23 15:37 ` Linus Torvalds
2000-11-23 15:44 ` Andi Kleen
[not found] ` <Pine.LNX.4.10.10011230825380.7992-100000@penguin.transmeta.com>
2000-11-23 17:39 ` Tigran Aivazian
2000-11-23 19:57 ` Andi Kleen
2000-11-23 20:38 ` Linus Torvalds
2000-11-23 20:59 ` Matti Aarnio [this message]
2000-11-23 21:31 ` Alexander Viro
2000-11-23 16:58 ` Ragnar Hojland Espinosa
2000-11-23 17:20 ` Linus Torvalds
2000-11-23 18:20 ` Ragnar Hojland Espinosa
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=20001123225900.E28963@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®