Hi all,

This is a summary of ruby-dev ML in these days.

[ruby-dev:28211] GC.stress

  TANAKA Akira proposed a new method GC.stress, which dispatches garbage
  collection more eagerly.  This method is useful to debug GC related
  problems.

  Matz agreed to him and this patch is committed in 1.9 branch.

[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.

[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 

[ruby-dev:28234] coding pragma

  In 1.9 branch, you can use "coding pragma" to tell the ruby interpreter
  the encoding of program file:

    #!/usr/bin/ruby
    # -*- coding: UTF-8 -*-

  KIMURA Koichi asked when this pragma is backported from 1.9 to 1.8.
  Nobuyoshi Nakada said that is difficult because current implementation
  calls ungetc() many times, which is not assured in C standards.  Ruby
  1.9 does not depend on stdio, multiple ungetc() call is not a problem.

  For details of coding pragma, see the thread from [ruby-core:04881].


-- Minero Aoki
ruby-dev summary index: http://i.loveruby.net/en/ruby-dev-summary.html