On Sat, 2 Jun 2001, Jason Wilkins wrote:

> Why, why, why? The compiler does an excellent job of creating a sane
> vsync wait loop. Is this really just a matter of doing it because

I modified mine slightly so it waits for 159 then for 160. Otherwise,
calling vsync() followed by vsync() the second call might execute while
VCOUNT still equals 160 thus it would instantly exit, rather than syncing
to the next VBLANK.

> everybody else is, or is there a real reason that this needs to be in
> assembly? I would love to find out, its bugging me. I would like to just

Prolly just that those coding a library (in ASM) are too lazy to make
their lib out of a mix of C and asm (like me :) besides "it'll only take a
mo"...

Pete
--
http://www.bits.bris.ac.uk/dooby/