Jonathan asked:
Then what of Xfractint? It is based on the integer/float version of Fractint.
Of course Xfractint, which already doesn't use integer math, should be integrated with the float only version, but only when we are ready to declare the float-only version the main (or only) version.
I do have a float only version, but it has been mangled by attempting to get the Allegro graphics package to work. The X-Window interface is still broken in it as well. And, even with that, the code is still vastly different from the float-only version. I do have the Xfractint float-only base source files that I started from, but they are at version 20.0 patch 11.
My intention was to get the Allegro version (float-only) of Xfractint working, then port it to djgpp to get back to the DOS/Windows environment.
You need to decide if you want to resurrect the Allegro version or in some other way preserve that work. How about you merge your latest patch with the float-only version as you have planned, then I merge the float only version with Xfractint (I don't think this will be hard), and then we stop work on the integer versions, or at least make the "official" versions the float only versions. If anyone wants to continue to backport the further development to the integer version, they are welcome, but we would declare the main tree to be the float-only version. If you agree with that plan, then you would need to decide what to do with your allegro version. I never quite got that development environment to work, thouigh I can't say I tried too hard. I think the only way to keep the allegro work alive (for the time being) would be to get those changes merged with in the same way the Xfractint/Fractint versions are merged, by sharing the same source files. Once that merging was done, with the integer version behind us, we could go forward with a single set of patches. At some point we might actually using CVS :-) Tim