Style-warnings and eval-when



On Thu, 2004-05-06 at 05:11, Andreas Eder wrote:
> Hi,
> is there still a lisp that we use for maxima, that cannot cope with
> the newer (?) situation names in eval-when?

The question is whether the ANSI build of GCL 2.6.2 can cope with the
modern version of eval-when. I don't know the answer off the top of my
head.

Unfortunately, in order to deal with the numerous warnings, you will
have to test things with GCL. Most of the non-standard forms are there
to support GCL. We only need to worry about 2.6.2 ANSI. (GCL 2.6.2 is
not quite released yet, but the current cvs 2.6.1 should be a very good
approximation of what 2.6.2 will be.)

> use of the old deprecated forms alone gives me more than 7000 warnings
> in a compile with sbcl.

Believe me, I am as annoyed by these warnings as anyone. I know
eval-when is particularly bad. (I think I am the original filer of the
bug that asks us to fix warnings.) It's just that we have had more
pressing issues in the meantime. I am very glad to have someone finally
addressing these problems.

> If not I'd edit all the relevant places - but how should I incorporate
> all the relevant patches? (cvs write access ?)

We have to establish the situation with GCL first.

--Jim