Hi,

> If you've got a fix ready to go, might as well check it in.

The original behaviour was a little  broken in that it wouldn't call toString 
at all, so I think the new 4.12 code is what was actually intended but it's 
hard to know.

Thanks,
Justin

Reply via email to