diff options
| author | Chip Salzenberg <chip@atlantic.net> | 1997-05-16 10:15:00 +1200 |
|---|---|---|
| committer | Chip Salzenberg <chip@atlantic.net> | 1997-05-16 10:15:00 +1200 |
| commit | 31412f2807c0207e41242206134c82bc4e8c566c (patch) | |
| tree | 1c9b61ae393f7ef41c00263eff38b4b6333365cb | |
| parent | f192e801bfe24f1bf6e24b397168a24ce021a5b7 (diff) | |
| download | perl-31412f2807c0207e41242206134c82bc4e8c566c.tar.gz | |
Explain that destruction order is not defined
(this is the same change as commit e195ec09596d2fe0e528026e48bc809e69e1165e, but as applied)
| -rw-r--r-- | pod/perltoot.pod | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/pod/perltoot.pod b/pod/perltoot.pod index 0c5b418c04..2f5634c58c 100644 --- a/pod/perltoot.pod +++ b/pod/perltoot.pod @@ -267,6 +267,9 @@ Because while a constructor is explicitly called, a destructor is not. Destruction happens automatically via Perl's garbage collection (GC) system, which is a quick but somewhat lazy reference-based GC system. To know what to call, Perl insists that the destructor be named DESTROY. +Perl's notion of the right time to call a destructor is not well-defined +currently, which is why your destructors should not rely on when they are +called. Why is DESTROY in all caps? Perl on occasion uses purely uppercase function names as a convention to indicate that the function will |