In article <456A13B2.26769.95B12A@twegner.swbell.net>, "Tim Wegner" <twegner@swbell.net> writes:
Just ifdef out integer math - the XFRACT ifdefs are already there.
This is what I've done so far. I've changed things like: #ifdef XFRACT ... #endif #ifndef XFRACT ... #endif to #if defined(XFRACT) || defined(_WIN32) and #if !defined(XFRACT) && !defined(_WIN32) on a case-by-case basis. This means that I am getting some stuff that xfractint leaves out, but not everything. For instance, I take the code path that deals with sound since my driver refactor dealt with that. (You'd want to use DirectX on Win32 for sound.) The XFRACT code path largely ignores anything with sound and implements stub routines to satisfy the linker. Back to the float-only version ... since it is a fork of the DOS code, wouldn't it be instructive to see diffs between the modules fractint and fractint-float? That would tell me the differences between the float-only version of fractint and the main version where I've made my changes. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>