Copying a null PDL implicitly reads data from the null PDL (to copy it), which
is invalid. The behavior is certainly allowed based on that.
That said, I think it would be more consistent and less surprising to either:
- retain nullness across copying and severing.
- throw an erro
Hi Diab-
I generally prefer have bug tickets be for
things that are broken while enhancements and
new features or API changes would be added as
feature request tickets. That said, I'm not usually
picky either---except when we're in feature freeze
for a new release and adding a feature request as
[I'm moving discussion of this here at Chris' request and top-posting,
which looks like is
the default behavior for this list]
Executive summary,
I expect PDL->null->copy to return a null piddle, it returns an empty one.
]
I don't read the docs in the same way. Here's the excerpt from PDL::Cor
