🚀 go-pugleaf

I thought I'd take a look at the Gemfast libraries the other day, so I
downloaded them from a.a. I wanted the sources since I'm using Lattice C,
which is not supported in binary form, so I downloaded the sources in the
form of several .lzh archives. I then tried to unarc them to my hard disk.
After about 30 minutes of waiting hoping in vain that lharc would stop
writing to the disk, I resigned myself to having to reboot the machine,
screwing up that partition of my hard disk in the process (rebooting when a
file is being written to and the FATs/directory haven't yet been updated).
Lharc had gotten seriously confused by the files, and tried to write something
to an infinitely large file. I've got 3 problems with this, all of which
reinforce the arguments people have made against lharc in the past:

1) Why does lharc not recognise that an archive is in a format it no longer
  supports/doesn't support yet (in my case the former, I suspect)

2) Why does Lharc not respond to an abort signal such as Ctrl-C, and stop
  what its doing cleanly (just doing a listing of the archive contents had
  the above effect as well, and even the low level, hacky, interrupt anything
  feature of my shell wouldn't stop it)

3) Why doesn't Lharc recognise the disk full condition in the above example
  and stop then. At least then the disk wouldn't be corrupted?

FWIW, I tried using lharc versions 2.??c, d, i and l (2.?? - I can't remember
the minor version number, is it 2.01?)

Kev