<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Eek, was this really the way to go?<BR>
It really seemed better before to me.<BR>
Before it was automatically portable without declaring the packed return type or NOHANG.<BR>
<BR>
- Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
From: jay.krell@cornell.edu<BR>To: hosking@elego.de; m3commit@elegosoft.com<BR>Subject: RE: [M3commit] CVS Update: cm3<BR>Date: Mon, 12 Jan 2009 10:11:17 +0000<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
> relies on particular endian-ness of the status<BR> > word they return. Really, those clients should<BR> > be using proper bit-shifts and bit-masks to extract<BR> > the right values rather than some endian- dependent RECORD layout defined in Uexec<BR> <BR> Wasn't Uwaitpid.c a good portable way to do exactly that? <BR> I guess it can be written in Modula-3 though, if the headers are cloned as they are.<BR> Aren't {I386,AMD64}_DARWIN broken here? <BR> Besides all "my" ports, which don't define those types. <BR> Yeah yeah, all I have to do is switch on endian and I can introduce them..<BR><BR> I'll see about Cygwin pthreads. <BR><BR> - Jay<BR><BR>> Date: Mon, 12 Jan 2009 10:20:33 +0000<BR>> To: m3commit@elegosoft.com<BR>> From: hosking@elego.de<BR>> Subject: [M3commit] CVS Update: cm3<BR>> <BR>> CVSROOT: /usr/cvs<BR>> Changes by: hosking@birch. 09/01/12 10:20:33<BR>> <BR>> Modified files:<BR>> cm3/m3-libs/m3core/src/thread/: ThreadPScheduler.m3 <BR>> ThreadPWait.m3 <BR>> cm3/m3-libs/m3core/src/thread/Common/: SchedulerPosix.i3 <BR>> cm3/m3-libs/m3core/src/unix/Common/: UtimeC.c Uwaitpid.i3 <BR>> m3makefile <BR>> cm3/m3-libs/libm3/src/os/POSIX/: ProcessPosixCommon.m3 <BR>> cm3/m3-libs/sysutils/src/POSIX/: SystemPosix.m3 m3makefile <BR>> <BR>> Log message:<BR>> Try to clean up mess with Process.Wait and System.Wait based on waitpid.<BR>> <BR>> Packing is now returned to Process.Wait and System.Wait where it used to be.<BR>> <BR>> Not sure if this re-packing is needed by clients, but should verify.<BR>> <BR><BR><BR></body>
</html>