[Pharo-project] Another finalization concern: error handling

Levente Uzonyi leves at elte.hu
Mon Oct 11 12:31:03 EDT 2010


On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:

> Henry,
>
> Ok, what valid use of multiple executors have I missed?

I described it earlier how the AXAnnouncements project uses this feature.


Levente

>
> Bill
>
>
>
> ________________________________________
> 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.
>>
>> Bill
>
> 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:
>
> Cheers,
> Henry
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>




More information about the Pharo-dev mailing list