mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
	ReiserFS List <reiserfs-list@namesys.com>,
	Edward Shishkin <edward@namesys.com>
Subject: Re: List of things requested by lkml for reiser4 inclusion (to review)
Date: Sat, 10 Sep 2005 00:51:42 -0400	[thread overview]
Message-ID: <5FDA2C74-F923-4695-A1B8-4355D445C073@mac.com> (raw)
In-Reply-To: <4321FCDA.60305@namesys.com>

On Sep 9, 2005, at 17:21:30, Hans Reiser wrote:
>>  It's huge CPP abuse
> can you define what that means? and how abuse differs from cleverness?
> This code was not my idea, but it seemed more cleverness than abuse to
> me when I read it.

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it."
   -- Brian Kernighan

Sometimes cleverness can be even worse than ordinary abuse :-D.  If the
code gets added to the kernel, then it should be debuggable (or at least
easily comprehensible) by a significant chunk of kernel developers, or
it will cause more problems than it solves.  I think that a type-safe
list system _would_ be a good addition, but make sure you comment it
heavily enough to make it really obvious, even to those of us who are
less than brilliant (like myself).

Cheers,
Kyle Moffett

--
Simple things should be simple and complex things should be possible
   -- Alan Kay




  reply	other threads:[~2005-09-10  4:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200509091817.39726.zam@namesys.com>
2005-09-09 17:36 ` Hans Reiser
2005-09-09 17:57   ` Chris Shoemaker
2005-09-09 20:42     ` Hans Reiser
2005-09-09 20:48       ` Nish Aravamudan
2005-09-09 20:49       ` Randy.Dunlap
2005-09-09 20:57       ` Chris Shoemaker
2005-09-09 18:57   ` Christoph Hellwig
2005-09-09 19:00     ` Christoph Hellwig
2005-09-09 21:21     ` Hans Reiser
2005-09-10  4:51       ` Kyle Moffett [this message]
2005-09-10  7:28         ` Paul Jackson
2005-09-09 21:41   ` Andrew Morton
2005-09-09 22:02     ` Hans Reiser
2005-09-12 18:08     ` Hans Reiser
2005-09-12 19:40       ` Horst von Brand
2005-09-10 10:14   ` Pekka Enberg

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=5FDA2C74-F923-4695-A1B8-4355D445C073@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=akpm@osdl.org \
    --cc=edward@namesys.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.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®