Bug #21476 for XML-Simple: SuppressEmpty does not work on an undefined value in arrayref.

Thu Sep 14 03:38:42 2006 kanna [...] fw.jellybean.jp - Ticket created

Subject:	SuppressEmpty does not work on an undefined value in arrayref.
Date:	Thu, 14 Sep 2006 16:38:09 +0900
To:	bug-XML-Simple [...] rt.cpan.org
From:	"かんな (Kanna)" <kanna [...] fw.jellybean.jp>

Hi, I use XML-Simple-2.14 and have a problem. The sample code below: print XMLout { xml => [undef] }; This prints: <opt> <xml></xml> </opt> It's OK, but adding SuppressEmpty: print XMLout { xml => [undef] }, SuppressEmpty => 1; Also prints: <opt> <xml></xml> </opt> I think this should be <opt></opt> because Show quoted text

> Setting the option to a true value (eg: 1) causes undefined values to

be skipped altogether on output. Is this a bug? Regards.

Thu Sep 14 03:58:13 2006 grantm [...] cpan.org - Correspondence added

From:

GRANTM [...] cpan.org

On Thu Sep 14 03:38:42 2006, kanna@fw.jellybean.jp wrote: Show quoted text

> Hi, I use XML-Simple-2.14 and have a problem. The sample code below: > > print XMLout { xml => [undef] }; > > This prints: > > <opt> > <xml></xml> > </opt> > > It's OK, but adding SuppressEmpty: > > print XMLout { xml => [undef] }, SuppressEmpty => 1; > > Also prints: > > <opt> > <xml></xml> > </opt> > > I think this should be <opt></opt> because >

> > Setting the option to a true value (eg: 1) causes undefined values to

> be skipped altogether on output. > > Is this a bug? > > Regards.

Yes, it does look like a bug. I release a fix soon. Regards Grant

Thu Sep 14 03:58:14 2006 The RT System itself - Status changed from 'new' to 'open'

Mon Oct 30 03:12:15 2006 grantm [...] cpan.org - Correspondence added

Fixed in release 2.15 (03-Oct-06)

Mon Oct 30 03:12:17 2006 grantm [...] cpan.org - Status changed from 'open' to 'resolved'