home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!spool.mu.edu!howland.reston.ans.net!paladin.american.edu!gatech!concert!samba!usenet
- From: Todd_Lewis@unc.edu (Todd M. Lewis)
- Subject: Re: Hardware bashing demo takes an OS friendly turn.
- Message-ID: <1993Jan11.162625.18539@samba.oit.unc.edu>
- Sender: usenet@samba.oit.unc.edu
- Nntp-Posting-Host: guitar.oit.unc.edu
- Organization: UNC Office of Information Technology
- References: <1993Jan8.150112.18376@imada.ou.dk>
- Date: Mon, 11 Jan 1993 16:26:25 GMT
- Lines: 17
-
- In article <1993Jan8.150112.18376@imada.ou.dk> breese@monet.imada.ou.dk (Bjoern
- Reese) writes:
- >Thanks to everybody who replied that WaitBlit() preserves the
- >scratch registers (condition codes doesn't matter). Now I will
- >definitely use WaitBlit().
-
- It was either Peter Cherna or Chris Green (I think) who gave
- a list of six tips for hardware coders:
- 1) Use WaitBlit(). 2) Use WaitBlit(). 3) Use WaitBlit().
- 4) Use WaitBlit(). 5) Use WaitBlit(). 6) Use WaitBlit().
- He convinced me. I sometimes open graphics.library, call WaitBlit()
- a few times, then close the library--even if I'm doing no graphics!
- I feel better about my programs, and they run just great! :-) :-)
- --
- _/_/_/ _/ Todd_Lewis@unc.edu You can lead a horse to
- _/ _/ utoddl@guitar.oit.unc.edu Mohammad, but you can't make
- _/ _/_/_/ a mountain drink a mole hill.
-