🚀 go-pugleaf

In article <1992Oct6.062407.14336@csis.dit.csiro.au> pwm@csis.dit.csiro.au (Peter Milne) writes:

>   Problem is that all of us ACL 3.1 users who have moved to NS 3.0 are
>   without a running lisp until ACL 4.1 appears (and they pay for it).
>   Now Bill Vrotney has mailed to this list that "Some wonderful guys who
>   wish to remain anonymous have come up with a simple fix for ACL 3.1.20
>   work under NeXTstep 3.0 ..."  Apparently their fix gets ACL going but
>   not the Objective C interface.  Bill has asked them for the fix so
>   he could post details, but so far nothing has been posted.
>
>   Well what one group of wonderful guys can do another can do too.
>   My suggestion is that we work together to try and come up with a
>   fix.  Anyone interested?

Ok, you've squeezed it out of me.

I DO have the fix from those "wonderful guys" that makes ACL work under NS
3.0. It is a patched version of the file ucl.o. But I do not have 3.0 to
verify it, although they did send me evidence that it does in fact work.

So the obvious question your probably wondering, "why not just post the
ucl.o file?". Well the reason that I haven't done that is that Franz in very
certain terms has informed me that if I do that it would be in violation of
their license agreement. However, Franz said that it would be ok with them
if I were to post a method that patched an existing user's ucl.o file. And
that is what I have been working on. I have been very busy and only have
parts of weekends to work on this.

If anyone has another approach, feel free to pursue it, as it will take me
awhile to produce the above method. In the mean time if you need Common Lisp
on NS 3.0 you might try AKCL (see the FAQ).

--
Bill Vrotney
BAH/Advanced Decision Systems