[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: KDE/kdevplatform [POSSIBLY UNSAFE]
From:       Matt Rogers <mattr () kde ! org>
Date:       2008-06-27 13:38:44
Message-ID: 200806270838.44726.mattr () kde ! org
[Download RAW message or body]

On Friday 27 June 2008 02:03:14 Andreas Pakulat wrote:
> On 26.06.08 18:42:54, Matt Rogers wrote:
> > On Thu, Jun 26, 2008 at 10:00:00AM +0000, Manuel Breugelmans wrote:
> > > SVN commit 824598 by mbreugel:
> > >
> > > Move xtest to kdevplatform & rename.
> >
> > I don't think that this makes sense. How is a unit testing library
> > a general plugin to have for more than just kdevelop? Why can't we
> > move this to the platform when another application actually needs
> > to use it instead of just assuming there will be another app that
> > will actually use it?
>
> You're misunderstanding. What is now in kdevplatform (or rather what
> should be there, I didn't have time yet to look into it closely) is a
> support library to write plugins for kdevelop that support running
> testcases for a specific unit testing framework. It aims in the same
> direction as eclipse TPTP (just not so extensive currently). Its AFAIK
> currently mostly the duplicated code from the 3 unit-test-framework
> implementations we have in kdevelop.
>
> Andreas

Thanks for clarifying that for me. I was indeed misunderstanding.

Even though I was misunderstanding, are we ready for this in kdevplatform now? 
If we released tomorrow, would we have issues with BC, for example? I know 
that we're not releasing tomorrow, but that's the mindset we should attempt to 
take with things like this, IMHO. 


_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]