🚀 go-pugleaf

Somebody condescended to give me the genesis of this thread.  To quote

	The problem is that Joe Blow (whoever started this thread)
	wrote a widget that creates a 32 meg temp file.  When
	applications exit with "exit(0);" the destroy callback for
	this widget is not called, and the file is not deleted.

GOOD HEAVENS!  Is THAT the problem???!!!!

[ ...grumble, grumble... ]

Every UN*X system that I've used allows the programmer to create a
file, and then unlink it from the file system.  As long as it is not
closed, it exists known only by the program until it exits.  (The
Morris worm exploited this behavior.)  When the program calls exit(),
the system calls clean everything up very nicely.

----

Ben

"It is a poor workman who blames his tools..."