On Wed, 10 Apr 2002, Nicholas Clark wrote: > The API doesn't define which side is "expected" and which side "got", > does it?
I believe it's defined (though perhaps not explicitly) as the first argument being the "got," and the second being the "expected." This is how the error messages print it, IIRC. > It's reasonable for it to be undefined if not-a-set is passed to the > "expected" side. But it's necessary for it to be well defined (and not > equal) if a bag is passed to the "got" side. All right. But how do you know if \["one", "two", "three"] is a bag or a set? Well, it's whatever you want it to be, until you add another "three" to it, at which point it can't be a set. Ah, the joys of an untyped language. cjs -- Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org Don't you know, in this new Dark Age, we're all light. --XTC
