[Chicken-users] Bug or feature? WRT testbase

[Robin Lee Powell]

I've noticed that define-expect-binary in testbase needs its
predicates to return #t; a true (non-#f) value is not sufficient.
This means that (define-expect-binary string=) because, despite
srfi-13's docs to the contrary:

    string=  s1 s2 [start1 end1 start2 end2] -> boolean

string= returns a number (the length of the match, I believe).

Loads srfi-13 doesn't help.

    EXPECTATION: Then: using translate with that pack and a plain string, we 
should get the original string back
    Expect string=
       Expected: "This is a test string."
    Unevaluated: "This is a test string."
      Evaluated: "This is a test string."
    Failed: Then: using translate with that pack and a plain string, we should 
get the original string back

So, bug or feature?  And, if it's a bug, is it a bug in string= or
testbase?  :)

For the record, it feel buggy to me.  Certainly the testbase output
is buggy looking, and I don't see anything in testbase's docs that
mentions this issue.

-Robin

-- 
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/