Dan Sugalski <[EMAIL PROTECTED]> writes: > I think I'd just as soon always call DESTROY in a predicable manner > and not do *anything* perlish at GC time. If nothing else it means > that we don't have to worry about having a valid perl context handy > when the GC runs. (Since threading the thing is a possibility we > might run into issues otherwise) So objects that get caught up in a circular reference chain don't get their DESTROYs called? I'm not sure I'd be up for that. In fact, I'm sure I *wouldn't* be up for that. Or are we gonna still need 'use WeakRef'? -- Piers
- RE: Meta-design Dan Sugalski
- RE: Meta-design Sam Tregar
- RE: Meta-design Dan Sugalski
- RE: Meta-design Sam Tregar
- RE: Meta-design Dan Sugalski
- RE: Meta-design Sam Tregar
- RE: Meta-design Buddha Buck
- Re: Meta-design Piers Cawley
- Guaranteed object destruction ... Dan Sugalski
- Re: Guaranteed object destruct... Nicholas Clark
- Re: Guaranteed object destruct... Piers Cawley
- Re: Guaranteed object destruct... Dan Sugalski
- Re: Guaranteed object destruct... Piers Cawley
- RE: Meta-design David Mitchell
- Re: Meta-design Simon Cozens
- Re: Meta-design Jarkko Hietaniemi
- Re: Meta-design mooring
- RE: Meta-design David Mitchell