<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
This change is suspicious. I think it leaks.<BR>
<BR>
Please see <A href="http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/libm3/src/os/WIN32/FSWin32.m3?rev=1.7;content-type=text%2Fplain">http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/libm3/src/os/WIN32/FSWin32.m3?rev=1.7;content-type=text%2Fplain</A><BR>
<BR>
for the pattern that is usually used.<BR>
<BR>
Granted, given the conservativeness of the collector -- it finds stuff in registers and the stack without a need for metadata telling it where the points are, and the fact that we no longer have VM-synchronization, I don't understand the need for the usual pattern. Maybe because it is willing to move stuff? Therefore a non-traced copy is made for C that won't ever move?<BR>
<BR>
- Jay<BR> <BR>> Date: Sat, 13 Mar 2010 02:11:24 +0000<BR>> To: m3commit@elegosoft.com<BR>> From: rcoleburn@elego.de<BR>> Subject: [M3commit] CVS Update: cm3<BR>> <BR>> CVSROOT: /usr/cvs<BR>> Changes by: rcoleburn@birch. 10/03/13 02:11:24<BR>> <BR>> Modified files:<BR>> cm3/examples/calling-c-win32/src/: OK.m3 <BR>> <BR>> Log message:<BR>> M3toC.TtoS has been renamed to M3toC.SharedTtoS, so make adjustments to Ok.m3 so that it will compile.--R.Coleburn<BR>> <BR> </body>
</html>