[Pharo-project] Another finalization concern: error handling
bschwab at anest.ufl.edu
Mon Oct 11 11:44:33 EDT 2010
Ok, what valid use of multiple executors have I missed?
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Henrik Johansen [henrik.s.johansen at veloxit.no]
Sent: Monday, October 11, 2010 11:23 AM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Oct 11, 2010, at 4:10 13PM, Schwab,Wilhelm K wrote:
> I am far more worried about having multiple executors per object (when did p=malloc();free(p);free(p);free(p) become good style?) than I am about getting the finalizer process itself completely robust at this point.
I fail to see how a blatantly obvious misuse of a feature becomes a valid argument against supporting that feature, or something you should worry alot about.
You can do Object become: nil, which is also not good style, but it's certainly not an valid argument for not allowing #become:.
Nor do I lose any sleep thinking of ways people could possibly abuse #become:
Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev