On Wed, 2005-01-12 at 14:00, Vadim V. Zhytnikov wrote:
> Unfortunately this is not so simple - there are other places which are
> not compatible with GCL 2.6.5.
Crud. Even though I would rather not maintain our own fork of defsystem,
it looks like we may have to do so for the time being.
However, there is one last thing to look at. I think Ray just replaced
defsystem.lisp with the current version from clocc. We had a few local
gcl modifications to defsystem which have therefore been lost. Would
restoring those patches solve the remaining problems?
> Obviously defsystem follows
> main GCL development branch.
As far as I can tell, defsystem doesn't follow GCL at all. There is a
real problem if we want to use pre-existing Lisp libraries: There are
two sets of people: people who write/maintain Lisp libraries and people
who use GCL. There seems to be *very* little overlap between the two
groups. Maybe GCL will seem more appealing to hard-core Lisp programmers
when it gets closer to the ANSI standard.
In the meantime, we have two possibilities: maintain our own defsystem
or patch defsystem for GCL and try to get them accepted into the main
defsystem branch. The latter might be the right thing to do, but I don't
have the energy to do it myself. A volunteer would be welcome.
> It seems that we have two
> options
>
> 1. keep our private copy of defsystem
Looks likely.
> 2. swith to GCL 2.7.X
>
> We should ask Camm about 2.
I *really* don't want to switch to GCL 2.7.x.
--Jim