Hi Richard, I guess it depends on what we are trying to achieve. I like the idea of having all the FRACTINT functionality in operating system independent code to link into our own programs like a JPEG library. Much of the ASM code is for high speed integer arithmetic. Do we need it in modern PCs with math coprocessors? The attraction in FRACTINT is the richness of features. The speed is less of an issue now. Just my thoughts anyhow. Thanks, Paul. ---------------------------------------------------------- Paul de Leeuw Computers NSW Central Coast, Australia Email: pdeleeuw@deleeuw.com.au www: < http://www.deleeuw.com.au> ABN 72 360 822 562 ---------------------------------------------------------- -----Original Message----- From: fractdev-bounces+pdeleeuw=telstra.com@mailman.xmission.com [mailto:fractdev-bounces+pdeleeuw=telstra.com@mailman.xmission.com] On Behalf Of Richard Sent: Monday, 29 January 2007 2:53 AM To: Fractint developer's list Subject: Re: [Fractdev] assembly code migration In article <000001c742d3$cfeda860$0301a8c0@Production>, "Paul" <pdeleeuw@deleeuw.com.au> writes:
I'm not sure that adding ASM code is the best way to go.
Its the easiest way. Either someone converts the existing assembly to 32-bit or someone converts the existing assembly to C. There is no C code corresponding to these routines; xfractint just didn't port them.
How does this affect the portability of the code across platforms?
Its not portable. But neither is the existing assembly language code.
Can the ASM be replaced with C equivalents?
It can be done, but I don't know assembly well enough to do this, at least not in any reasonable time frame. -- "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/> _______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev