🚀 go-pugleaf

In article <FAT.95Sep20151221@fat.cnit.nsk.su>, fat@cnit.nsk.su (Dmitry V.
Irtegov) wrote:

> If you lock handles before each use and unlock them after,
> your code inflates 2-3 times,

Unless all your code is doing is a system call just about every line (and
I can't think of any useful non-trival program that does this), the
additional code is nowhere near that inflated.  A couple of percent at
most.

> and if you don't you have werid
> bugs when you pass pointer outside of lock/unlock region.

Why aren't you passing the handle?  Micro-optimized code usually ends up
buggier than well thought out code.  Don't do microoptimizations until you
know there is a bottleneck.

> Been there, done that.

That says more about your skill as a programmer than it does about the
Mac's memory scheme.

> Handle memory management is crap 
> and nobody can convince me otherwise.

That says more about you being a close-minded person than it does about
the Mac's memory scheme.

> Basically, handles is a patetic attempt to emulate hardware MMU in software.

Not true.  The problem doesn't go away with VM; it merely gets delayed. 
One could argue that if you can delay it enough, it isn't worth the
additional complexity to deal with it, but that certainly wasn't true in
the 80s, when RAM and disk space were damn expensive.

> 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.

You mean (possibly) writing a page to disk and reading a different page
from disk?  These are fairly slow operations.

> 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.

But the customers, not the programmers, get to choose (with their
pocketbooks) what environment they are willing to run the software on. 
Personally, if everybody had 4G of RAM and a couple of terabytes of disk
space, as a programmer my job would be a heck of a lot easier.  Should I
send you my address so you can give me this hardware?
-- 
        Nevin ":-)" Liber       nevin@CS.Arizona.EDU    (520) 293-2799