Roddey suggests I send in the patch for codewarrior I'd be happy to. One thing I should point out is that supporting codewarrior for Windows will make your Mac programmers happy, because I suspect the usual reason someone uses Codewarrior on windows is because they're using codewarrior on the Mac, and the two compilers are bundled together. It makes cross-platform development easier too - you can generate mac powerpc and 68000 code on windows, and windows x86 code on the mac, and even debug over the wire from a foreign machine.
My question is, how do you want my patches? I have the compiler specific header file (I called it MWCWDefs.hpp), small changes to AutoSense.hpp, I used Erik Ulevik's windows transcoder that uses the Windows API rather than the ANSI widechar routines, and I rolled my own memset (Metrowerks is being _very_ prompt about addressing the memset problem; I suspect Ron Leichty never sleeps; he seems to address programmer's problems 24X7 on the net). Also there's the issue of the project file. The regular codewarrior project is a binary file. But it can be exported as an XML file (!) that would be more amenable to CVS. Certain settings that are important to getting it to build right need to be in the project file, just like in a Makefile. So I could either put it all in a few folders and zip them up, or I could make a folder tree that reflects the actual heirarchy of the original sources, with just the changes sources, and zip that up, or you could give me access to CVS. But actually I'd rather not just check in changes myself at this point; I'd rather that someone else did the checking, partially because I haven't used CVS all that much, particularly not on windows. Mike Crawford [EMAIL PROTECTED] http://www.goingware.com
