libraries and environments

[jsshapiro@earthlink.net]

In message <v03130300b17be1a676cb@[208.138.21.1]>, Norman Hardy writes:
> First I am confused about what it means to pass a domain key. If A passes
> such a key to B, which domain is the passed key to, A or B?

My note was indeed confusing.

In this case, I was talking about library code that was linked into
the domains.  What I should have written was that the *register
numbers* of the keys were being passed to this library code.  This is
to ensure that the library code does not need to make assumptions
about the register locations of particular capabilities.

What was finding was that a great number of library routines want to
use the domain key to the current process, or some scratch key
register.  I was wondering if there were a few keys that are so
frequently used that it was worth just locking them into designated
registers (by convention) to avoid the argument passing overhead.


shap