All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ralph Ulrich <eulenreich@gmx.de>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: The reiser4 programming style is recursive?
Date: Thu, 11 Dec 2008 01:23:33 +0300	[thread overview]
Message-ID: <49404165.6050806@gmail.com> (raw)
In-Reply-To: <494035ED.4000706@gmx.de>

Ralph Ulrich wrote:
> Is it true that the programming style of reiser4 is recursive style

what is a definition of recursive programming style?

>  and
> that this kind of style was rejected from the kernel developers?
>   

AFAIK they were unhappy with assertions and "coding nits"  like
if (foo) {
        bar();
}
Eventually akpm said that assertions are okay and guys send
cleanup patches against other issues once in a while.

> If  true: How much effort would it be to recode reiser4 to a style which
> has a chance of inclusion in the linux kernel?
>
> And if there will be a recoding effort to be made, wouldn't it be a
> great idea to use a cleaner and more modern programming language link D ?
>
> Thanks in advance for answering my more general questions.
> Ralph
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   


  parent reply	other threads:[~2008-12-10 22:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 21:34 The reiser4 programming style is recursive? Ralph Ulrich
2008-12-10 21:41 ` Teran McKinney
2008-12-10 22:07   ` Ralph Ulrich
2008-12-10 22:21     ` David Backeberg
2008-12-11  0:09       ` Ralph Ulrich
2008-12-11  4:49     ` Toby Thain
2008-12-10 22:23 ` Edward Shishkin [this message]
2008-12-11  0:23   ` Ralph Ulrich
2008-12-11 16:57     ` Edward Shishkin
2008-12-11 17:37       ` Ralph Ulrich
2008-12-11 18:12         ` Edward Shishkin
2008-12-11 19:05           ` Ralph
2008-12-11 22:56             ` Edward Shishkin
2008-12-12 16:21               ` Ralph
2008-12-13 19:30                 ` Edward Shishkin
2008-12-14 15:24                   ` The... reiser4 with no ambiguity Ralph Ulrich
2008-12-14 19:17                     ` Edward Shishkin
2008-12-16  0:59                       ` Ralph Ulrich
2008-12-17 21:49                         ` Edward Shishkin
2008-12-18 12:28                           ` Ralph Ulrich
2008-12-21 13:38                             ` Edward Shishkin
2008-12-11  0:46   ` The reiser4 .... why it is the future Ralph Ulrich
2008-12-11 11:35     ` The reiser4 .... what it really means Ralph Ulrich
2008-12-11 12:22       ` Ralph Ulrich
2008-12-11 14:36         ` Alexander Lyamin
2008-12-11 17:11           ` The reiser4 ....SDK for experiments outside kernel Ralph
2008-12-11 19:10             ` Edward Shishkin
2008-12-11 19:56               ` Ralph
2008-12-11 23:03                 ` Edward Shishkin
2008-12-11 23:04                 ` Christian Stroetmann OntoLab
2008-12-12  0:54                   ` Ralph
2008-12-11 14:56       ` The reiser4 .... what it really means Christian Stroetmann OntoLab
  -- strict thread matches above, loose matches on Subject: below --
2008-12-12 16:48 The reiser4 programming style is recursive? Mat

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=49404165.6050806@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=eulenreich@gmx.de \
    --cc=reiserfs-devel@vger.kernel.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.