linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
	Carl Spalletta <cspalletta@yahoo.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Dan Carpenter <d_carpenter@sbcglobal.net>
Subject: Re: inventing the wheel?
Date: Fri, 30 May 2003 12:26:30 -0300	[thread overview]
Message-ID: <20030530122629.C1617@almesberger.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0305301111160.30122@chaos>; from root@chaos.analogic.com on Fri, May 30, 2003 at 11:12:38AM -0400

Richard B. Johnson wrote:
> The problem with 'correctness" is in the definition
> of 'correct'. In many cases there are hundreds of
> methods that can be used to implement a particular
> software algorithm.

Of course. Your example would probably be too low-level for
most such checkers, and might better be handled by run-time
checks (e.g. through something like valgrind).

Also, a template check wouldn't have to cover all equivalent
coding variants. E.g. if the template just allows one kind
of loop, it's probably always acceptable to change code that
uses an equivalent alternative.

Furthermore, if someone figures out a way for doing things
more efficiently, it should be easier to update drivers that
conform to a well-known status quo ante.

> One can, however, create an analysis engine that determines
> compliance with certain rules and, or, certain templates.

Yes, that's exactly what I mean.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

      reply	other threads:[~2003-05-30 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 18:05 inventing the wheel? Carl Spalletta
2003-05-27 22:09 ` Carl-Daniel Hailfinger
2003-05-28 12:28   ` Carl Spalletta
2003-05-30 14:30   ` Werner Almesberger
2003-05-30 15:12     ` Richard B. Johnson
2003-05-30 15:26       ` Werner Almesberger [this message]

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=20030530122629.C1617@almesberger.net \
    --to=wa@almesberger.net \
    --cc=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=cspalletta@yahoo.com \
    --cc=d_carpenter@sbcglobal.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --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;
as well as URLs for NNTP newsgroup(s).