projects / p5sagit/p5-mst-13.2.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f192e80)
Explain that destruction order is not defined
authorGurusamy Sarathy <gsar@engin.umich.edu>
Thu, 15 May 1997 06:00:23 +0000 (02:00 -0400)
committerChip Salzenberg <chip@atlantic.net>
Thu, 15 May 1997 22:15:00 +0000 (10:15 +1200)
commite195ec09596d2fe0e528026e48bc809e69e1165e
tree081cf61df726ba2280f1cf8f11a05548ac4c6a64tree | snapshot
parentf192e801bfe24f1bf6e24b397168a24ce021a5b7commit | diff
Explain that destruction order is not defined

Subject: Re: perl debugger problem with object destructors?

On Wed, 14 May 1997 15:12:38 MDT, Tom Christiansen wrote:
>
>Actually, deterministic destruction/finalization is oft-deemed
>a feature.   If you could check what perltoot has to say about destructors,
>gsar, and suggest an appropriate patch if necessary, I'd appreciate it.

I'd say something like this:

p5p-msgid: 199705150600.CAA13550@aatma.engin.umich.edu
pod/perltoot.pod diff | blob | blame | history
Unnamed repository; edit this file to name it for gitweb.