🚀 go-pugleaf

I have two questions regarding graphics programming using THINK C's Class
Library:

1. I take it that the Class Library eliminates the explicit use of an event
   loop (the details being handled in Application).  Is this true?
2. What if I want to write a program that is constantly drawing, but is
   interrupted by user actions.  The Class Library seems set up to work well
   with static documents that only change under user control.  But I want
   to write something like a Mandelbrot program which continues to draw
   until the user clicks to zoom in.  Should my drawing become a Chore?

I also have a question about writing a very custom profiler:

3. I would like to write my own profiler that generates an entry for
   every single instruction, noting the instruction's location and the
   memory (if any) addressed by the instruction.  Is this easily done on
   such a fine-grained level?
--


Wayne Folta          (folta@cs.umd.edu  128.8.128.8)