<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Really? Isn't it considerably safer to have a function declaration list the actual type instead of requiring all the callers to cast?<br>I left ThreadF safe and I think I left it all much better than this.<br>Safety is not a boolean. I'd much rather have a lot of UNTRACED REFs to specific types than a bunch of ADDRESSes.<br><br> - Jay<br><br><br>> Date: Tue, 8 Sep 2009 17:16:19 +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/09/08 17:16:19<br>> <br>> Modified files:<br>> cm3/m3-libs/m3core/src/runtime/common/: RTAllocator.m3 <br>> cm3/m3-libs/m3core/src/thread/Common/: m3makefile <br>> cm3/m3-libs/m3core/src/thread/POSIX/: ThreadF.i3 ThreadPosix.m3 <br>> cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadF.i3 <br>> ThreadPThread.m3 <br>> cm3/m3-libs/m3core/src/thread/WIN32/: ThreadF.i3 <br>> ThreadInternal.i3 <br>> ThreadWin32.m3 <br>> <br>> Log message:<br>> Forgot to propagate safety fix for MyHeapState to WIN32 and POSIX. Fixed now, which allows me<br>> to undo Jay's unfortunate bandaid. ThreadF is safe as god intended.<br>> <br></body>
</html>