>>> <klaus.berndl@...> seems to think that:
>Eric M. Ludlam wrote:
>> There is certainly a discrepency between the doc and the
>> functionality. As you are the first to mention this eggregeous error,
>> perhaps these functions should just be deleted in favor of direct
>> calls to inversion..
>Yes, sounds senseful - so i have replaced semantic-required-version
>in my working-copy of semantic-regtest.el by a call to inversion...
>BTW: I took a look into PRERELEASE_CHECKLIST and found "use semantic-regtest.el".
>IMHO a good pointer... because i wrote this library more than 1 year ago i thought
>i it would maybe a good idea to test this stuff with current cedet ;-)
>First result: Fixing the inversion-stuff.
>But in general it works pretty smart (some selfpraising ;-)....
>So i would create for all test-files in semantic/test a reference-output with
>active cedet1.0beta3 and store them also in semantic/test... Then i will
>run a regression test with semantic-regtest-run-test for all test-files with
>active current CVS-cedet and check where are the differences... the output-
>files of these tests i will also store in semantic/test. This files can
>are openend in a smart major-mode semantic-regtest-mode when
>semantic-regtest.el is loaded. So if there are parsing-differences betweeen
>current CVS and cedet1.0beta3 we can decide if they are ok and if yes, we make
>the regtest-outputs with CVS-cedet the new referencial-outputs so we get for
>future releases a good regression-test-base.
That sounds useful. The reference output could be in semanticdb form,
but not necessarilly in a semanticdb.cache file. If you create
a file, you can use this:
(let ((obj semanticdb-current-table))
to create the file. I think you can then use `eieio-persistent-read'
on the filename. I haven't tried it so who knows.
[ ... ]
>BTW: In the past semantic-regtest.el was also mean to allow regression-tests
>between semantic-1.4-parsers and the semantic-2.X-parsers - therefore
>semantic-regtest itself is written with the semantic-1.4-API so it can run
>under semantic-1.4 too....
>Hmm, i currently mull over if it would make sense to port this lib to the
>semantic-2.0-API but then this lib can not run under semantic-1.4 and create
>test-output for semantic-1.4-parsers... But do we need this really? What do you
[ ... ]
It seems useful to test against 1.4 compatibility for 1.0.x releases,
and perhaps save it as semantic-regtest-1.4.el and provide an updated
one for later. I would like to someday obsolete the 1.4 API
sometime. It is very large.
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org