[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: sander's diff library

From: B. W. Fitzpatrick <fitz_at_red-bean.com>
Date: 2003-02-06 04:48:55 CET

Ben Collins-Sussman <sussman@collab.net> writes:
>
> So Sander's internal diff/diff3 library is finished, and passes make
> check. All we need to do now is give it some serious testing, and
> bam, no more pain-in-the-butt diff and diff3 behavior on different
> OSes.
>
> On the one hand, we need a good test suite for the library. On the
> other hand, Sander recently announced that people could test the
> library by simply switching part of their working copy, and poof, svn
> would start using it.
>
> I think the problem here is that 'svn switch' is a bit too much;
> nobody wants to make that kind of commitment yet. The Chicago folks
> have an idea, though.
>
> Sander -- I'd like to propose that you integrate your code into trunk
> permanently. Create a new cmdline switch (--difflib?) that causes the
> commandline client to to use the internal diff library instead of
> calling out to GNU diff/diff3. Testing your code then becomes a
> runtime issue, rather than a compiletime one. I think that will
> significantly lower the bar for testing.
>
> Eventually, the --difflib switch can be deleted. But it would great
> for now. (IIRC, this is method by which we first started getting i18n
> code exercised.)

+1. This diff library is something that the BSD/Apache style license
community has been talking about doing for years, and Sander's
actually *done* it! Let's make it as easy as possible for everyone to
try it and test it out.

-Fitz

PS Sander for President!

--
Brian W. Fitzpatrick    <fitz_at_red-bean.com>   http://www.red-bean.com/fitz/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 6 04:48:41 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.