🚀 go-pugleaf

In article <wade-1809952212460001@f182-067.net.wisc.edu> wade@macc.wisc.edu (Wade E. Masshardt) writes:
> In article <43kai7INNjvp@anvil.ugrad.cs.ubc.ca>, c2a192@ugrad.cs.ubc.ca
> (Kazimir Kylheku) wrote:

>>But if you lock down handles, you are fighting the OS in its efforts to
>>eliminate fragmentation.

>Unless you have brain, in which case you lock the handle just before you
>are going to use it, then unlock it as soon as you are finished.  Duh.

If you lock handles before each use and unlock them after,
your code inflates 2-3 times, and if you don't you have werid
bugs when you pass pointer outside of lock/unlock region.
Been there, done that. Handle memory management is crap 
and nobody can convince me otherwise.

Basically, handles is a patetic attempt to emulate hardware MMU in software.
Virtual address is basically a handle, but MMU hardware does equivalent
of locking and unlocking for you, which is order of magnitude faster and 
easier. Anyway, multitasking environment without a MMU is disaster,
no matter what you would do.

Win16 and Mac programmers are forced to fight with handles,
when in any decent environment (including win32 here) programmers
just rely on hardware doing all handle-related stuff for them.

Cheers,
	Fat Brother.

Fatal Error: Couldn't enter Windows, use Doors.