Re: [Chicken-users] Please do not drop 'thread-terminate!' from the SRFI 18 impl

[Kon Lovett]

Hi Folks,

One more controversy ;-)

I guess I just prefer social rather than legal prescriptions.  
Prohibition is an attack on symptoms & not causes.

Sadly we have a philosophical issue here. I am not for the general use  
of unsafe operations but against proscription.

I commiserate with those feeling the evangelical impulse to spread the  
word to the benighted masses while recognizing the danger in  
unfettered access. However, there are methods to produce a restricted  
denotation for problematic forms.

(We need a discussion group on the subject of Chicken Parallelism.)

On Aug 8, 2008, at 7:43 PM, Elf wrote:

> On Fri, 8 Aug 2008, Vincent Manis wrote:
<snip>
> im against removing thread-terminate! and friends because theyre  
> useful.

Useful, perhaps? In very rare, restricted, special circumstances.  
Maybe kinda like "set-cdr!".

>  id
> rather deprecate mutexes

See above.

> and the like for a cleaner system of currency,

Ok, go for it. I just don't think removing a "feature" is a feature.

> or
> (at the very least) augment thread-terminate! in such a way that it  
> waits to
> terminate until the held mutexes (mutii? mutices?) are dropped.

(Don't you mean mooses ;-)

Maybe a (thread-terminate!/mutex-wait [MUTEX ...]), where a null  
argument list is wait on all mutex, procedure rather than a semantic  
change to an existing procedure?

> -elf
<snip>

Best Wishes,
Kon