All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Clausen <clausen@gnu.org>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: reiserfs-list@namesys.com
Subject: Re: aal_assert()
Date: Sat, 11 Jan 2003 00:26:28 +1100	[thread overview]
Message-ID: <20030110132628.GA1056@gnu.org> (raw)
In-Reply-To: <15901.23872.24060.68353@laputa.namesys.com>

On Thu, Jan 09, 2003 at 02:30:08PM +0300, Nikita Danilov wrote:
> These "message ids" are traditional way reiserfs code uses to identify
> errors (probably because early during development preprocessor features
> were unknown) and Hans feels himself attached to them emotionally. :-)

Well, I'll give some arguments against this scheme:

(1) it's more code, more work, more space, etc.  Programmers are
minimalists, and adding extra stuff feels dirty.

(2) "ids" are the Wrong Way to identify things... things should
be identified by their essence, not by tags.  This is the whole
OO vs relational database flamewar.  Relational databases
(the "by essense/being, not tag") won, game over.

You don't query things by tags, but by what they are.

I know this is all quite subjective... I just wanted to provide
some emotional arguments as well as rational ones *grin*

Another thing: I'd like to see libaal reused in all file system
tool implementations.  That's my main motivation for cleaning it
up.  My first target is ntfs...

Cheers,
Andrew


  parent reply	other threads:[~2003-01-10 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31  0:54 aal_assert() Andrew Clausen
2003-01-10  7:22 ` aal_assert() Yury Umanets
2003-01-10 13:36   ` aal_assert() Andrew Clausen
2003-01-10 14:12     ` aal_assert() Yury Umanets
     [not found] ` <15901.23872.24060.68353@laputa.namesys.com>
2003-01-10 13:26   ` Andrew Clausen [this message]
2003-01-10 13:19     ` aal_assert() Yury Umanets

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=20030110132628.GA1056@gnu.org \
    --to=clausen@gnu.org \
    --cc=Nikita@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 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.