|
Boost : |
From: Jonathan Turkanis (technews_at_[hidden])
Date: 2005-02-21 13:46:37
Angus Leeming wrote:
> I've recently picked up the baton of what the library itself would
> need and started trying to discuss the possible alternatives. See
> here:
>
> http://www.devel.lyx.org/~leeming/process/
>
> It seems to me that the hardest part of writing such a library isn't
> the code to spawn the process in the first place at all. Rather it's the
> code to monitor the status of a running process and to notify the rest of
> the code when it has exited. I suspect that an Alexandrescu-style
> policy-based design will be needed, but with a twist. Once a
> singleton process_monitor variable is created, invocation of any
> other policy should become an error.
Could you elaborate a bit on how the policy-based design would look? In
particular, are you saying it would resemble the Loki singleton, or just that it
would involve policies of some sort? Also, I'm not sure what you mean by
invoking the policies.
Best,
Jonathan
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk