gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Gcl-devel] load-time value support, closed compile bugs in ANSItest


From: Mike Thomas
Subject: RE: [Gcl-devel] load-time value support, closed compile bugs in ANSItest suite
Date: Wed, 24 Nov 2004 11:02:39 +1000

Hi Paul.

| I'm seeing this (built with --enable-ansi on a Redhat 9 x86 machine
| this morning), then doing (load "gclload.lsp") in a running lisp:

Thanks very much for this feedback, it is very helpful.

A quick eyeball shows that RATIONAL.1, some PATHNAME and DIRECTORY tests and
most importantly, every OPEN.* test failed on Windows.

I was looking at the swathe of open test failures last night and found that
the test forms I tried all actually worked if just entered at a GCL prompt.
In the test log they are failing like this:

OPEN.1

Expected value: "abcdefghij"
Actual value: #<CONDITIONS::INTERNAL-SIMPLE-ERROR.259>.

despite being OK at the command prompt.

OPEN.2 gives:

Expected value: "abcdefghij"
Actual value: #<CONDITIONS::INTERNAL-SIMPLE-ERROR.260>.

OPEN.3:

Expected value: "abcdefghij"
Actual value: #<CONDITIONS::INTERNAL-SIMPLE-ERROR.261>.

That is, the eroor number increases by one each time??  I'll follow up as
time permits - will have to find out what internal-simple-errors are first.

Cheers

Mike Thomas






reply via email to

[Prev in Thread] Current Thread [Next in Thread]