                 JeffreyBobs -- A ShadeBob demo by

  \--/    \--/    /---\    \--/--\\   \--/=\\   \--/  \-----\
   ||\\  //||   /       \   ||    ||   ||   ||   ||    | |\  \
   || \\// ||  |         |  ||____//   ||==<<    ||    | | | |
   ||  \/  ||   \  X X  /   ||   \\    ||   ||   ||    | |/  /
  /--\    /--\   | | | |   /--\  /--\ /--\==//  /--\  /-----/
                 |_|_|_|

                 /----\____           ________
                /           \    /\   \   ___  \
               /  /|   /|   /   /  \   \  \  \  \
              /  / /  / /  /   / /\ \   \  \  \  \
             /  / /  / /  /   /  /\  \   \  \  \  \
            /__/ /__/ /__/   /__/  \__\   \__\  \__\


Written completely in Turbo Pascal 7.0 (well, with a minimal amount
of Asm thrown in).

I wrote this demo in about five days (after my girlfriend suggested the
idea), as a break from the real demo I've been working on for a two weeks.
I haven't had too much time, what with school, work, and all my little
projects, but I thought this might be a good example program on how
to code shadebob type objects (having never done it before, I would
hope you'd be kind enough *NOT* to flame ;)  It's also a good example
of how *NOT TO* code!

Please, if you're just learning Pascal, *DO NOT LOOK AT THIS CODE*!
I have one word to describe it: spaghetti!  Assembly is more comprehensible!

If someone would like to optimize my routines, please send $20...

(Sorry)

If you optimize my code (ooh, tough...) or do something more cool than
I can do with it, please send a copy by me (just because I'm curious
to see what could be done with my code).

I haven't really gotten any responses back, but I'm a glutton for
feedback.  I'll be gone over the summer (to Poland, to visit my family),
but I'd appreciate it if you could e-mail comments, coding suggestions,
job offers, etc. to my girlfriend (kestrel@ccwf.cc.utexas.edu).

This isn't the best demo in the world.  But then, I'm not a genius (like
an 18 year old friend of mine, or like Josh Jensen).  I have to work at
my code.  Live with it.  Flames (such as "gosh, you duplicated this code
four times" or "didn't you know that a reverse Brensenham loop would 
compensate for the gain of nanoseconds...") should be directed to the
ol' bitbucket (/dev/null).

That's pretty much it.  Strip whatever you need out of the code.  Be careful
with the clock interrupt -- DON'T GO MESSING WITH STUFF YOU DON'T KNOW
ABOUT!

(Nothing should happen, but I take no responsibility for anything my
program or code does to your computer.  By executing the program or
looking at the code, you are agreeing to that...)

Oh...the title "JeffreyBobs" is a (bad) pun.  My full name (thanks, Dad)
is Jeffrey Bob Berthiaume, Jr.  Not Robert.  Says so on m'birth certificate.
           ^^^

Ciao!

                      Morbid "God, I'm tired" Man

