Warnings generated when serializing undef

[EvanCarroll]

May want to silence these.

Use of uninitialized value $data in pattern match (m//) at /opt/cpanel/perl5/536/site_lib/TOML/Tiny/Writer.pm line 73.
Use of uninitialized value $data in pattern match (m//) at /opt/cpanel/perl5/536/site_lib/TOML/Tiny/Writer.pm line 74.
Use of uninitialized value $arg in substitution (s///) at /opt/cpanel/perl5/536/site_lib/TOML/Tiny/Writer.pm line 212.
Use of uninitialized value $arg in substitution (s///) at /opt/cpanel/perl5/536/site_lib/TOML/Tiny/Writer.pm line 213.
Use of uninitialized value $arg in concatenation (.) or string at /opt/cpanel/perl5/536/site_lib/TOML/Tiny/Writer.pm line 215.

[oalders]

Is there a minimal case to reproduce this?

[EvanCarroll]

use TOML::Tiny;

my $db = { 
          'mysql' => {
                       'host' => '127.0.0.1',
                       'socket' => undef
                     }
        };

my $p = TOML::Tiny->new( strict => 1 );
print $p->encode($db);

It does not like values set to undef

[oalders]

Does the TOML spec allow for undef?

[EvanCarroll]

No, so I would think you could handle it by providing a mapping function, replacement string, or just dying and saying "we don't handle undef, and neither does TOML". But, I wouldn't generate warnings from inside the library.

[oalders]

Ok, thanks! I'm not really invested in this module right now, but if someone comes along with a PR I'm happy to deal with that.