From: Trans Date: 2007-12-10T22:52:44+09:00 Subject: Re: redefineable not operator On Dec 10, 3:33 am, Yukihiro Matsumoto wrote: > Hi, > > In message "Re: redefineable not operator" > on Mon, 10 Dec 2007 17:17:51 +0900, murphy writes: > > |why such heavy syntax changes, two weaks before the release of Ruby > |1.9.1? I mean, I'm happy that changes are always possible here, but I > |thought 1.9 was fixed some time ago. it's really confusing for me, since > |I don't know any (English) website that's summarizing what's going on > |recently... > | > |so there is no 1.9-stable branch? no feature-fixed release candidates > |before 1.9.1? > > As I said before we try our best to stabilize features before > Christmas. 1.9.1 on Christmas will not be as stable as you (or we) > expected. > > |- it seems I can no longer rely on !x returning a boolean :( > | how do I make my !!x hacks 1.9-compatible? > > We don't encourage to redefine ! operator, unless you know what you > are going to do. Are you feeling okay, Matz? The ability to redefine ! is about as fundamental as it gets. I'm quite surprised to see you let your conservative guard down... may I re-recommend Peter Vanbroekhoven's percent literal patch now (http:// rubyforge.org/projects/suby/)? ;-) But on a more pressing note, may I ask if more problematic issues are being looked at too -- in light of the pending release? For instance, I've not heard if the autoload issue, I've mentioned before, is being addressed --that bug is a BIG DEAL for me. And there appears to be a many other important issues listed in Tracker (though granted, I can't really judge their merits). Okay... I guess this is one of those "please no new features; fix the bugs we got" requests ;-) Thanks, T.