🚀 go-pugleaf

In article <5vE-N3F6nTB@site71.ping.at> wsog@site71.ping.at (Walter Sommergruber) writes:

> It think it's always better to think a few minutes about bad errors rather
> than hoping that it will never happen...
> Send a message and then shutdown the program (closing files, releasing OS- 
> resources,...). Or do you like core dumps so much ?

There's a lot to say for core dumps, actually.  If you have a
development environment and an operating system that supports core
dumps in the first palce, then there's probably a lot of useful
information in a core dump that can tell you just what went wrong
where.  Printing out an error message and dumping core might not be a
very slick way of dealing with fatal errors, but you can do worse.
-- 
  Matt Austern                             He showed his lower teeth.  "We 
  matt@physics.berkeley.edu                all have flaws," he said, "and 
  http://dogbert.lbl.gov/~matt             mine is being wicked."