From: David Flanagan <david@...>
Date: 2007-12-10T15:40:07+09:00
Subject: redefineable not operator

Matz,

I saw the following commit the other day:

  Commit by matz  ::  r14162 /trunk/ (7 files in 2 dirs):

     * parse.y (expr): redefinable not (!) operator.
     * parse.y (arg): ditto.
     * object.c (rb_obj_not): new method "!".
     * object.c (rb_obj_not_equal): new method "!=".
     * object.c (rb_obj_not_match): new method "!~".

Could you comment on this change, please?  Are you making these 
defineable just because there is no reason they can't be?  Or is there 
some more significant reason?  Are any core classes going to redefine 
any of these?

Thanks!

	David