In article <45843DB8.6496.CA434@twegner.swbell.net>, "Tim Wegner" <twegner@swbell.net> writes:
CVS says Tim added this code on revision 1.3.
Heh heh - subversion has a "blame" command that shows you exactly who is responsible for each line of code :-)
CVS has "annotate" that shows you line-by-line the revision where that line was modified and who did the commit :-).
No. The bf code has a greater dynamic range than bn code and we should keep it. I revisited arbitrary precision last summer after a long hiatus in support of a new fractal type I'm working on. If that define is from last summer and not in any of Jonathan's public developer versions, it's just an experiment that I was doing. I would like that julia bn logic to remain but the USEBN define could be commented out so the logic for the arbitrary precision types reverts to bf math as it was.
Well, its in the HEAD, so that's the way its "shipping" right now. I'll comment out the #define USEBN on my branch. Thanks. -- "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/>