Alex Ferguson wrote:
What's the state of the art as regards calling Haskell functions from
'the outside world'? I note that Haskell Direct has this in its
manifesto, but says "currently unsupported". Does that mean a moderate
size black hole at the centre of something still potentially
ing that we may be opening Pandora's Box here.
Surely, there must be a more elegant solution that resolves all of these
problems. If I come up with it, I'll let you know. :)
- Michael Hobbs
x_inv) (int y_inv))
- Michael Hobbs
y. I haven't thought enough
about it to come up with a concrete solution. If this is good enough,
I'll see if I can noodle on it some more.
- Michael Hobbs
lly.
...or querying the system time, down to the nanosecond...
- Michael Hobbs
Michael Hobbs wrote:
(We're assuming that we can't lock them both simultaneously)
I knew I should have read the literature on deadlock avoidance before
posting that message. :-/ In fact, I should have used the word
"atomically" above instead of "simultaneously". As it
Michael Hobbs wrote:
Here's my stab at it. (NB: This is simply an off-the-cuff attempt. It
looks like it should work right, but it is far from rigorously tested or
analyzed.)
grumble/
I discovered a path that would cause a deadlock in that code as well.
However, I have a change that /should
George Russell wrote:
Does the phrase "Dining Philosophers Problem" ring a bell with anyone?
And AFAIK, the existing solutions to that problem requires a knowledge
of who all the philosophers are and what they are attempting to do. That
gets back to the issue of having a global value that
