<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Jay:</DIV>
<DIV> </DIV>
<DIV>I have both console and gui programs built using 4.1 that do pull stuff out of the environment. I've not noticed any problems with either mode.</DIV>
<DIV> </DIV>
<DIV>From my perspective, the old 4.1 seems more reliable than the current system in a number of respects. I have a new project with a hard deadline that I would like to use the new cm3 system for, but until these problems (pixmaps, buildstandalone, environ vars, serial i/o, etc.) can be resolved, I'm going to keep using 4.1 for my production work.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy<BR><BR>>>> Jay <jayk123@hotmail.com> 5/8/2008 2:46 PM >>><BR><A href="http://modula3.elegosoft.com/cm3/uploaded-archives/">http://modula3.elegosoft.com/cm3/uploaded-archives/</A><BR> <BR><A href="http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-WIN32-NT386-d5.7.0.zip">http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-WIN32-NT386-d5.7.0.zip</A><BR><A href="http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-WIN32-NT386-d5.7.0.zip">http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-WIN32-NT386-d5.7.0.zip</A><BR><A href="http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-WIN32-NT386-d5.7.0-symbols.zip">http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-WIN32-NT386-d5.7.0-symbols.zip</A><BR> <BR>These should have:<BR> latest quake extensions <BR> set relation fixes <BR> other set fixes revealed through dynamic linking of one regression test <BR> hypothetical ability to cross-build to AMD64_LINUX, AMD64_DARWIN <BR> one jmpbuf size for all NT386 configurations (NT386, NT386GNU, NT386MINGNU) <BR> <BR>Built with Visual C++ 9.0 Express, so you'll want:<BR><A href="http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en">http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en</A><BR> <BR> <BR>Still more work to do though, e.g. assertion failures in unit tests, pixmap..<BR> <BR>Fuller disclosure:<BR>Something is leaking memory on my system such that "everything" starts "failing" and I have to reboot.<BR>This isn't Modula-3 related.<BR>Hopefully these files aren't damaged as a result.<BR>Must be some buggy driver or something..<BR> <BR>Aside:<BR> The environment variable thingy has been bugging me a long time and I finally looked deeper at it.<BR>It appears broken in CM3 4.x. I didn't check 3.x yet.<BR>I'm still mulling a fix, and haven't run a repro of the break, but it's not a big deal either way.<BR>Basically console apps use main that takes char** and gui apps use WinMain that doesn't get environment variables but the generated code calls GetEvironmentStrings() which returns null separated strings.<BR>Must be that hardly anyone uses environment variables in Modula-3 on Win32 for this to have lingered so long, at least gui apps.<BR> <BR> - Jay<BR></DIV></BODY></HTML>