MARK HARRISON said to DOUG WILSON on 05-30-97:
==============================================
MH| (( QUOTING = From: Doug Wilson  To: Lance Reynolds ))
MH|  DW> This will let you know if your counter function is working
  |  DW> right. The prints() function prints to your screen but doesn't
  |  DW> get sent out over the modem.  Once things are working you can
  |  DW> remove the line and recompile to clean up the display.
MH| Hello Doug,
  | Since a prints does however make a change to your screen display.
  | I have found that status_wind() is a much better way to insert
  | test messages to yourself.
Hiya, Mark -
Yeah, I use status_wind() too, depending on what I'm trying to
do.  Status_wind() is fine if you know you'll be watching intently
at the time, but you can't scroll back thru the buffer to see
what happened after the fact.  And if you are trying to follow
several different parts of the code my dismal memory makes it
tough to recall which window popped up when.
For most of my temporary debugging, I use prints() which allows
me to compare the scroll back buffer with the code to really
figure out what is or is not happening..
...
 * OLX 2.2 * Get your mind out of the gutter - you're blocking my view
--- RBBSMail/386 v0.997
---------------