Re: clisp/src TODO,1.88,1.89

[Sam S. <sd...@gn...>]

> * Bruno Haible <oe...@py...> [2005-06-07 22:43:19 +0200]:
>
> Sam wrote:
>> > +bind-eval.tst failure on Linux/amd64 [sam]
>>
>> this one is yours.
>
> No, this feature is your code. I looked at it and found that I don't
> understand the code. So it's better if you fix it, since you
> understand it.

nope, I don't.

>> > +workaround for extra comma in _clisp.1 [sam]
>>
>> forget about it.
>> it has been fixed in the XSL CVS.
>
> Will you upgrade your tools to this version, or is it too risky?

I am tracking this issue.
if they will not get their act together before we release, it can be
fixed by hand for the release.

>> > +regression: resolution of logical pathnames is broken, try
>> > +   (compile-file (logical-pathname "FOO.LISP")) [sam]

fixed. all the release blockers are now yours.


PS. has the FRESH-LINE issue been settled?
    <http://article.gmane.org/gmane.lisp.clisp.devel:14259>

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.honestreporting.com> <http://www.dhimmi.com/>
<http://www.memri.org/> <http://www.palestinefacts.org/>
There are two ways to write error-free programs; only the third one works.