gcl-devel
[Top][All Lists]
Advanced

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

Re: [Gcl-devel] ansi-test


From: Sam Steingold
Subject: Re: [Gcl-devel] ansi-test
Date: 17 Dec 2002 10:31:08 -0500
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50

> * In message <address@hidden>
> * On the subject of "Re: [Gcl-devel] ansi-test"
> * Sent on Tue, 17 Dec 2002 07:30:11 -0600
> * Honorable "Paul F. Dietz" <address@hidden> writes:
>
> Sam Steingold wrote:
> 
> > 1. The tests do not carry a note of _what_ they test.
> >    Paul said that he creates the tests by reading CLHS.
> >    This every test should carry a note at to what section it tests.
> 
> Generally (not universally) the tests are grouped by page in the
> CLHS.  These tests, for example, are testing the DEFSTRUCT page.

sure.  but what aspect?  (I am probably asking too much here :-)

> There are something like 6500 tests now.  Since few or very few of
> them fail on good implementations, it's a lot easier on me if I can
> just document on demand when tests fail.

that's the whole point!!!
you should document tests _as you write them_.
every DEFTEST should have a documentation slot.

> I'll see about getting rid of the gensyms here.

thanks.

> As Christophe noted, this has to be printed with *print-circle* bound
> to t to be reread properly.

then you should bind *print-circle* when printing such tests.


-- 
Sam Steingold (http://www.podval.org/~sds) running RedHat8 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
186,000 Miles per Second.  It's not just a good idea.  IT'S THE LAW.



reply via email to

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