[M3devel] variations of waitpid..?

[Jay]

 > If someone uses waitpid they get what they paid for. 
 
But someone is us -- m3core/libm3 (I think just m3core), sysutils, and then cm3 uses them.
 
I guess there is a point that this "grand new interface" SchedulerPosix.DoesWaitPidYield has precious few users.
 (It isn't grand. It takes no parameters and just returns a boolean, hardcoded, depending on thread library.)
 
m3core now (today) uses it internally -- no need for a public interface.
Sysutils can't use it until the baseline m3core is newer, so arguably, not a user.
  Instead (today) sysutils uses m3core's m3makefiles to decide the value.
 
Heck, waitpid is therefore only used internally by m3core, and sysutils.
If sysutils could be (partly) merged into m3core, then m3core's waitpid need not be public.
 
 - Jay> CC: mika> From: hosking> To: jay> Subject: Re: [M3devel] variations of waitpid..?> Date: Thu, 1 Jan 2009 12:29:24 +1100> > If someone uses waitpid they get what they paid for.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090101/23d46148/attachment-0002.html>