Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got this mail from the author of Devel::TrackObjects regarding strange warnings:
Hi,
$tracked->[0] is the object itself.
If you print it it will stringify it. Stringification is overloaded
in Date::Time using Date::Time::_stringify, which will use ymd and hms
to stringify the object.
If the Date::Time object itself contains no $self->{local_c} yet the
values for sprintf in ymd and hms will be undef which causes the
warnings.
So this is not really a bug in DateTime, because they never intended
for somebody to stringify some internal objects. But it's not a bug
in Devel::TrackObjects either.
Let's just say, they are not made to work close together.
But I've worked now around this overloading when debugging is enabled
(just released 0.5, see https://github.com/noxxi/p5-devel-trackobjects)
and so can you: