🚀 go-pugleaf

One comment I have regarding this trend.

What happens if you depress ctrl-break and your program is enough over
DOS not to stop at that moment (i.e. if you disabled ctrl-break by
something like signal() or other mean).

In one case (kbhit?), the value returned is either 0 or the character
received.  But ctrl-break is also returning a value of 0!
In other words, the program will freeze or exit if you typed ctrl-break!

My work-around consisted in writing my own kbhit function in Assembler.
I called it keyin().

Instead of returning the character received, it tests the zero flag and
return a response accordingly (0 or 1 for instance).  I think both
bioskey(1) and kbhit return the input character, so this must be
checked.  Also, this particular behaviour (I consider this as a bug)
was found in Zortech compiler.  No idea if Borland, Microsoft or
other will do the same.

One last word : if you know how to process ctrl-break, you probably
already have a work-around or set the BREAK switch so it does not harm.

-- 
  \_\    Denis Beauregard  *  internet:beaurega@ireq.hydro.qc.ca
 /   \   Genealogiste officiel : Beauregard/Jarret/Jarest/Vincent
J   __>  Barthelemy Jarret (1471) -> Andre Jarret, sieur de Beauregard (1665)
\_.-===   -> Denis Beauregard (1992)                  Opinions ? Et pis non !