CEDET

Hi,

Eric M. Ludlam wrote:
> Klaus,
>=20
>   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.

Thoughts?

Ciao,
Klaus

P.S.

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=20
semantic-regtest itself is written with the semantic-1.4-API so it can =
run=20
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
think?

Klaus,

  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..

Eric

>>> <klaus.berndl@...> seems to think that:
>Hi all,
>
>Here is the docstring of semantic-required-version:
>
>"semantic-require-version is a compiled Lisp function in `semantic'.
>(semantic-require-version MAJOR MINOR &optional BETA)
>
>Non-nil if this version of semantic does not satisfy a specific version.
>Arguments can be:
>
>  (MAJOR MINOR &optional BETA)
>
>  Values MAJOR and MINOR must be integers.  BETA can be an integer, or
>excluded if a released version is required.
>
>It is assumed that if the current version is newer than that specified,
>everything passes.  Exceptions occur when known incompatibilities are
>introduced."
>
>Not that the arguments are needed as integers - at least the doctsring says ;-)
>
>But when i try to run: (semantic-require-version 2 0 1) i get this error:
>
>Debugger entered--Lisp error: (wrong-type-argument sequencep 1)
>  semantic-require-version(2 0 1)
>  eval((semantic-require-version 2 0 1))
>  eval-last-sexp-1(nil)
>  eval-last-sexp(nil)
>* call-interactively(eval-last-sexp)
>
>When i call: (semantic-require-version "2" "0" "1")
>all is working fine. 
>
>The problem comes from the current impl. of semantic-required-version
>which calls `concat' with integers which leads to this error. So
>M-: (concat "." 1) produces the same error - tested with current
>stable GNU Emacs 21.3.1!
>
>Maybe there are other *-required-version function in the cedet-suite
>with the same problem, that either the docstring is wrong or the impl.
>
>Ciao,
>Klaus
>