|
From: | Eric Ludlam |
Subject: | bug#20507: 25.0.50 eieio and packages depending on it |
Date: | Tue, 05 May 2015 20:58:19 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 05/05/2015 02:56 PM, Stefan Monnier wrote:
>I think I am able to contribute to that. But please tell me >more precisely which are the goals so that I do not make >something that is not in the spec ! Or simply tell me if >there's a good place to know what has to be done with the eieio >project and all its dependencies.Mostly what needs to be done is to make sure that old code still works, and when it doesn't decide whether it should be fixed by changing EIEIO to be more bug-compatible or by changing the old code.
Hi Stefan,CEDET has an extensive test suite, but most of it hasn't been merged into Emacs' tests. I suspect the easiest way for you to get some good coverage is to pull CEDET from the sourceforge repository, build it using your development version of Emacs, and then do:
make utest-batch and when that works make itest-batchThe unit tests were failing for me with Emacs 25 a couple months back and I fixed a bunch of issues to make it work with some of the planned changes to eieio. I'm not sure where it stands today as I haven't had time to mess with it recently.
The tests include all the tools that use eieio, and exercise a wide range of features from Semantic's completion to the SRecode insertion macros. If you pass these tests, I'd have high confidence your eieio changes are in good shape.
The unit tests usually only take a minute or so, but the interactive tests can take several minutes. The tests require you have many external tools installed which I assume you do, such as make, automake, gcc, and a few other things.
Eric
[Prev in Thread] | Current Thread | [Next in Thread] |