Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the PPI CPAN distribution.

Report information
The Basics
Id: 31563
Status: resolved
Priority: 0/
Queue: PPI

People
Owner: Nobody in particular
Requestors: TELS [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.201
Fixed in: (no value)



Subject: documentation of "delete" method is wrong
remove The documentation of "delete" is wrong, it contains a copy&paste version from the "remove" method: delete For a given "PPI::Element", the "remove" method will remove it from its parent, immediately deleting the "Element" and all of its children (if it has any). Returns true if the "Element" was successfully deleted, or "undef" if an error occurs while trying to remove the "Ele‐ ment". Also, the documentation could make more clear what the actual difference between "remove" and "delete" is, if there is any.
On Sat Dec 15 12:19:53 2007, TELS wrote: Show quoted text
> remove > The documentation of "delete" is wrong, it contains a copy&paste version > from the "remove" method: > > delete > > For a given "PPI::Element", the "remove" method will remove it > from its parent, immediately deleting the "Element" and all > of its children (if it has any). > > Returns true if the "Element" was successfully deleted, or > "undef" if an error occurs while trying to remove the "Ele‐ > ment". > > Also, the documentation could make more clear what the actual difference > between "remove" and "delete" is, if there is any.
Hmm, the only difference is that "delete" additionally calls DESTROY explicitly. I suspect this was originally intended to get around memory cycles, but I *think* this is no longer a problem due to the current %_PARENT implementation, but I'm not entirely sure. Adam? Chris
This was fixed at some point in the past, so i'm closing this.