<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
I strongly suspect that Target.EOL can go away and just use Wr.EOL instead.<BR>
Or even just \n.<BR>
<BR>
<BR>
Cross builds are fairly rare, esp. cross between NT and Posix, and very<BR>
many tools treat \n, \r\n, and perhaps \r the same, so even<BR>
crossing NT <=> Posix doesn't likely matter.<BR>
ie. it works, assuming you have a cross m3cg (ie: mingwin/cygwin hosted for NT hosts)<BR>
<BR>
<BR>
gcc, Visual C++ compiler, m3front, all treat \r and \r\n the same.<BR>
(witness all our *.h, *.c, *.i3, *.m3 files use \r\n)<BR>
I think we have some tools that don't understand \r\n, but in my opinion that is a bug.<BR>
All three formats should be treated the same.<BR>
<BR>
<BR>
I know notepad doesn't display \n well, and Sun cc might not like \r\n.<BR>
I know some compiler I used recently was picky, but "many" compilers are not.<BR>
cmd might be ok with \n.<BR>
Python calls it "universal newlines", treating all three formats the same.<BR>
<BR>
<BR>
C:\dev2\cm3.2\m3-sys\cm3\src\Utils.m3(190):PROCEDURE CopyText (old, new: TEXT) =<BR>C:\dev2\cm3.2\m3-sys\m3middle\src\M3File.m3(61):PROCEDURE CopyText (src, dest: TEXT; eol: TEXT) RAISES {OSError.E} =<BR><BR>
<BR>
probably leave alone, except that they don't treat \r correctly if you consider the historical Apple behavior.<BR>
There are three formats, not two.<BR>
<BR>
<BR>
Anyway, it's not a big deal. I think my problem here is solved by the change to m3x86.m3 I already made.<BR>
I'll put Target.EOL back on my machine.<BR>
<BR>
<BR>
- Jay<BR> </body>
</html>