comment on

Thank you for the replies.

I'm not sure I realized that "no warnings" wouldn't affect warnings emitted by XML::Simple. I think I knew this in the back of my head, but I added that at some point and it must have worked--perhaps accidentally, combined with some other change--so I never considered it.

I also don't know why the warnings re-started recently.

In any case, I'm absolutely sure that $data itself was defined.

However, after a bunch more testing, I realized that I was getting these warnings for any undefined values in the data. And then I realized that the error was that SuppressEmpty => 0 was a mistake--it's supposed to be SuppressEmpty => undef (or the empty string). When I made this change, the warnings went away, and I got my desired empty XML in the output.

I have no idea why it (seemed to) work at one point and then go back to not working. However, it's clear that the SuppressEmpty setting was the right way to fix it.

Thanks again.

In reply to Re: "no warnings 'uninitialized'" failing by jest
in thread "no warnings 'uninitialized'" failing by jest

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks