Since SEAL is going to be rewritten from scratch in C++, perhaps GCC 3.1 ought to be used to develop it in order to ensure that SEAL works with GCC 3.x. This would also be to the advantage, since GCC 3.1 has a better C++ ABI and is much more fully compliant with the current C++ standards.

well at present the code we have for seal3 (is very crap and sxl is F***ed Up) so i made a C ver with original sxl and is basicly the same but in C both copile Owen ver and my C ver_________________leon pegg
W_W_N_UK@YAHOO.CO.UKWhen Hell is full, the dead will walk the earth...

well, since we're starting from scratch i don't see that there's any point in using antique GCC versions, 3.1 is perfectly feasable at this stage, Leon, if S3 is meant to be written in C++ then what is the benefit of converting it to C?_________________http://www.theopencd.org/ - OpenSource for the Masses

djgpp is the de facto 32-bit standard compiler, the only other option is OpenWatcom. I say stick to djgpp.

As for gcc versions, even I have 3.03... (Not g++) I think that the latest compiler is probably the way to go, or at least try to build for 3.03 at a minimum._________________RMF-DOS, Dapple on SourceForge ...
Dosius Software - Bringing Back the Best!

well, since SEAL3 is cross platform it wont just be DOS compilers, this is a very old thread and development has already started on SEAL3, GCC3.x compatible AFAIK._________________http://www.theopencd.org/ - OpenSource for the Masses

Open Source software never dies, it just goes to sub without return _________________ The name is DaNo, and he's got a licence to program in VB, C and Assembly Language.
What more can we say about a living legend?
Programmer of the DaNoOS: http://home.planet.nl/~esch0090