B. Tommy Jensen wrote:
> Does anyone know whether this is a deliberate design choice in 1.9, or 
> is it a mistake that should be corrected?
This seems to be the same problem I reported in ruby-core:13824. ko1 
considered this to be a bug and wanted to correct it.

-- 
Florian Frank