From: Austin Ziegler <halostatue@...>
Date: 2006-02-03T00:18:05+09:00
Subject: Re: ruby-dev summary 28206-28273

On 02/02/06, Minero Aoki <aamine@loveruby.net> wrote:
> [ruby-dev:28217] ANDCALL operator
>
>   Nobuyoshi Nakada suggested a new operator `&?' (this notation is temporary)
>   which evaluates left-hand-side expression, and if it is true then call
>   right-hand-side method.  For example:
>
>     if a[1] and a[1].strip.empty?
>                 ||
>     if a[1] &? strip.empty?
>
>     h["key"] and h["key"].dispatch
>                 ||
>     h["key"] &? dispatch
>
>   The motivation of this operator is to avoid duplication of expression.
>
>   Takaaki Tateishi proposed another idea, Object#nil? with block
>   (again, this name is temporary).
>
>     a[1].nil? {|str| str.strip.empty? }
>     h["key"].nil? {|h| h.dispatch }
>
>   This issue is still open.

I would prefer the latter, but it doesn't completely solve the repeated
expression issue. Worse, the use of #nil? would mean that anyone who has
overridden #nil? would have broken behaviour -- and the behaviour is the
inverse of what I'd expect. (That is, I'd expect the block to be called
*if* the item is nil, not if it isn't nil.)

> [ruby-dev:28233] 1.8.5 release plan?
>   URABE Shyouhei proposed a rough release plan of Ruby 1.8.5,
>   assuming the release date is 1st Apr.
>
>     Week 0 (2/4) : Decide a plan.
>     Week 1 (2/11): Prohibit any feature changes on 1.8 branch.
>     Week 2 (2/18): Fixing bugs on 1.8 branch.
>     Week 3 (2/25): Preview 1; Prohibit non-critical bug fixes.
>     Week 4 (3/4) : Validate preview 1.
>     Week 5 (3/11): Preview 2; Prohibit non-critical bug fixes without release engineer.
>     Week 6 (3/18): Validate preview 2.
>     Week 7 (3/25): Preview 3; Prohibit any changes without release engineer.
>     Week 8 (4/1) : 1.8.5 release

Might I suggest not having a 4/1 release because of Poisson d'Avril?

-austin
--
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca