On 06 Jul 2005, at 09:30, Eric Mahurin wrote:

> --- Yukihiro Matsumoto <matz / ruby-lang.org> wrote:
>
>> <dooby / d10.karoo.co.uk> writes:
>>
>> |I expected you to say that this was intentionally provided
>> |as a "third state":
>> |
>> |true  - positive pattern match result
>> |nil   - negative pattern match result
>> |false - don't know (no match was done)
>>
>> Hmm, sorry for behaving unexpectedly.  But I like your idea.
>> Ryan, what do you think?
>>
>>                             matz.
>>
>
> Should nil be don't know and false be mismatch?  That would be
> consistent with <=> which returns nil if the items aren't
> comparable.  Maybe the same should be done with == and === -
> return nil instead of false when the 2 objects can't be
> compared.

$ ruby -e 'p "f" =~ /x/'
nil

-- 
Eric Hodel - drbrain / segment7.net - http://segment7.net
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04