Re: Guidelines? (And a quick note about the website)

[The Greene Family <topcoder@mindspring.com>]

Good idea!  I've put a lot of thought about that, because sound mixing can
take alot of CPU usage especially when throwing 3D in the mix.  It's not so
bad on higher-end systems, but with lower-end Intel chips, you can see it,
big time, so assembly counts.  But for systems where assembly just isn't
going to happen C can stick.  I guess maybe i should look into assembly on
other systems maybe?

Derek


At 04:07 PM 3/25/99 +0100, you wrote:
>You could do it like in Crystal Space. Keep all routines in C so you always
>have the C fallback if needed but provide assembly versions of time critical
>C functions which can optionally be used. Using this technique Crystal Space
>can run on Linux, Solaris, IRIS/SGI, FreeBSD, BeOS, OS/2, Windows, DOS,
>NextStep, OpenStep, Rhapsody, Macintosh, and Amiga while still using
>maximum optimized assembly on systems that support it.
>
>Of course the disadvantage of this is that you need to maintain two versions
>of that particular routine. But you should only do this for routines that 
>absolutely
>need this (like the inner texture mapping loop) and that are not very likely
>to change (so at the end stage of the project).
>
>And NASM is a good choice for assembler as it is portable on Intel platforms.
>
>Greetings,
>
>
>
>--
>==============================================================================
>Jorrit.Tyberghein@uz.kuleuven.ac.be, University Hospitals KU Leuven BELGIUM
>
>"You can't trample infidels when you're a tortoise. I mean, all you could
>do is give them a meaningful look."
>        -- (Terry Pratchett, Small Gods)
>==============================================================================
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: penguinplay-unsubscribe@sunsite.auc.dk
>For additional commands, e-mail: penguinplay-help@sunsite.auc.dk