From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Lexical comparator, was Re: the battle against SCO
Date: Tue, 16 Sep 2003 08:48:53 +1000 [thread overview]
Message-ID: <20030915224853.GA27957@minnie.tuhs.org> (raw)
In-Reply-To: <20030915204355.EB9311E5D@minnie.tuhs.org>
On Mon, Sep 15, 2003 at 04:39:31PM -0400, Norman Wilson wrote:
> It does seem sensible to me for the Linux community to do its best to
> hunt down any infringing code... But that ought to be a matter of basic
> ethics, having nothing to do with SCO. I doubt it is likely to make
> much difference to the court battle anyway... I think it's
> a good idea to remove any infringements that are there now, even if they
> are trivial ones; but let's not fool ourselves that it will pull SCO's
> fangs to do so.
For me it's not just a matter of defeating SCO, it's also one of sheer
indignation in the face of Saganesque FUD ("billions and billions of
lines of code"). I seriously want to know if there's even the tiniest
possibility that SCO is right, or if they're are just Smoking Crack Often.
While we're on the topic, I saw esr's code shredder/comparator that works
on lines of code. This isn't going to work if variables get renamed etc.
I'm writing a code comparator that works on a lexical basis, comparing
C tokens. It's only going to be proof of concept (i.e. slow), but I
should have it done by week's end and I'll pop a notice in here when it's
ready.
Cheers,
Warren
next prev parent reply other threads:[~2003-09-15 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 20:39 [TUHS] Fwd: Helping in " Norman Wilson
2003-09-15 22:48 ` Warren Toomey [this message]
2003-09-16 0:46 ` [TUHS] Lexical comparator, was " Rhys Weatherley
2003-09-18 2:56 ` [TUHS] Lexical comparator Warren Toomey
2003-09-16 3:01 ` [TUHS] Fwd: Helping in the battle against SCO M. Warner Losh
2003-09-16 0:02 [TUHS] Lexical comparator, was " Norman Wilson
2003-09-16 1:35 ` Robert Brockway
2003-09-16 3:10 ` M. Warner Losh
2003-09-16 2:11 Norman Wilson
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=20030915224853.GA27957@minnie.tuhs.org \
--to=wkt@tuhs.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 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).