Subject: | |
From: | |
Reply To: | |
Date: | Fri, 30 May 2008 21:06:16 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
In message <001201c8c20e$0cc11410$a0f23e45@DJFJQK21>, Walter J. Murray
<[log in to unmask]> writes
>Dave wrote:
>> Hope so, but someone else said it wouldn't work because of a deadlock
>>if daddy kills off junior while junior is waiting for a lock. I
>>haven't seen anyone else refute that, and I wouldn't claim to know.
>>We do only really simple locking and I've never had to pay attention
>>to deadlock rules.
>Yes, that might be a problem. Not a deadlock, per se, but I don't know
>what happens if you try to kill a child process while it's waiting on an
>unconditional lock request to be satisfied.
>> Meanwhile, is this still at the prison system ? Anyone else find it
>>ironic that they might have issues with locking strategy ? :)
>You think that's bad? Try programming in an environment where you're
>not allowed to use "escape" sequences!
>Walter
It's useful to have software in a prison, though. Whenever you need a
new block of cells, all you have to do is open a spreadsheet :-)
--
Roy Brown 'Have nothing in your houses that you do not know to be
Kelmscott Ltd useful, or believe to be beautiful' William Morris
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|