debug.m is the E module equivalent to the C linked library debug.lib.
If you already know this linked library, you can skip this introduction
and directly go to the TECHNICAL section.
    For those who don't know this link library, let me give you a little
explanation of its interest. Indeed, it contains simple input/output
functions for the serial port. Thanks to them, you can use a remote debug-
ging terminal linked to your Amiga via the serial port. But nobody have
a debugging terminal linked to his Amiga :-) So a solution is to used
Sushi which is developper tool (but also available on aminet) to intercept
raw serial debugging output and to redirect it to a simple CON window.
So every Amiga can take benefit from these function. But what is the
interest for a sample Amiga E user in relation to the WriteF() procedure ?
I see two advantages :
    - debugging output isn't mixed with normal output
    - you can't use functions like WriteF(), PrintF(), etc (in fact, all
the dos.library function) outside a process context, in other words, you
MUST use debug.m functions instead for exec tasks, devices, handlers, etc

 PERMSSN    UID  GID    PACKED    SIZE  RATIO     CRC       STAMP          NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
-rw-r--r--  5553/200       565    1852  30.5% -lh5- 6eb0 Aug 15  1994 debug.asm
-rw-r--r--  5553/200      1395    2729  51.1% -lh5- 239c Oct 10  1994 debug.doc
-rw-r--r--  5553/200       365     540  67.6% -lh5- 957e Aug 15  1994 debug.m
-rw-r--r--  5553/200       370     516  71.7% -lh5- 13c5 Aug 15  1994 debug.o
---------- ----------- ------- ------- ------ ---------- ------------ -------------
 Total         4 files    2695    5637  47.8%            Oct 11  1994