Re: Why I need to use C for screen graphics
Andrew Katz wrote:
> still 60% slower.
I still read that as good, well actually, amazing. Bad point is Eu creates a
sequence to call a c_func, good point is it checks no of args, whether func/proc,
etc, and if it craps out on you most times it says straightaway what line it died
on, and if not, trace(3) does. C gives few clues.
> Note that for most applications this is not an issue. But my application
> needs to write thousands of tiny little lines to make curved shapes.
Agreed; there are times to resort to a crappy but fast language.
I write quite a bit in asm, btw, no matter my bitches over trace(), and I get
that OllyDbg is just about as good as it could be, I actually really like it, but
basically it still sucks in comparison.
Regards,
Pete
|
Not Categorized, Please Help
|
|
