[Gcl-devel] Fwd: Rev 1.31 of src/nparse.lisp breaks windows build of CVS HEAD

[Robert Dodier]

Forwarding this message from the Maxima mailing list.
Context: http://sourceforge.net/support/tracker.php?aid=1483203
Any comments would be much appreciated.

All the best, & thanks for your help.
Robert Dodier

---------- Forwarded message ----------
From: Vadim V. Zhytnikov <address@hidden>
Date: Nov 11, 2006 11:45 PM
Subject: Re: Rev 1.31 of src/nparse.lisp breaks windows build of CVS HEAD
To: Robert Dodier <address@hidden>
Cc: "Billinghurst, David (CALCRTS)"
<address@hidden>, address@hidden


Robert Dodier writes:
> On 9/5/06, Billinghurst, David (CALCRTS)
> <address@hidden> wrote:
>
> > Revision 1.31 of src/nparse.lisp breaks windows build of CVS HEAD with
> > gcl-2.6.7  As noted in the changelog, it hadn't been tested on windows.
> >
> > http://maxima.cvs.sourceforge.net/maxima/maxima/src/nparse.lisp?view=log

Finally I've got some time to see what is going here
with 1483203 bug and both on Unix and Windows.
Unfortunately results aren't good.  So something must be
changed here but I don't quite understand what is the best way.

UNIX:

I've tested Maxima 5.10.0 (no fix for nparse applied yet)
and Maxima CVS which includes nparse fix (Rev. 1.31)
with gcl 2.6.7 and 2.6.8 cvs 26.10.2006.
And here are some results:

1. Maxima 5.10.0 + gcl 2.6.7 - problem with trailing space is
here as expected.

2. Maxima 5.10.0 + gcl 2.6.8 - no problem is observed.
So probably the problem is fixed on gcl side.

3. Maxima CVS + gcl 2.6.7 - once again no problems as expected.
Fix to nparce.lisp works fine in this situation.

4. Maxima CVS + gcl 2.6.8 - Bad!  Now input prompt is printed
twice after expression with trailing.  This is probably result of
new gcl 2.6.8 behavior.

Windows:

On Windows I've checked gcl 2.6.8 only and the really unpleasant
thing is that result is quite different. First, I don't see that
anything is broken.  Build went smooth and both Maxima versions
5.10.0 and CVS appear to be in workable state.  But!
As long as the trailing space bug 1483203 is concerned
both these versions behaves precisely like bug was not
fixed at all - like 1 on UNIX.

I'm puzzled.

--
     Vadim V. Zhytnikov

      <address@hidden>
     <address@hidden>