On Wed, Jan 29, 2003 at 08:24:33PM -0800, Aaron Lehmann wrote: > Since this problem seems to have been fixed in HEAD, and possibly in > the 3.3 branch (I haven't tested it) Update - 3.3 DOES have the bug.