ljknews wrote:

At 11:38 AM -0700 7/13/04, Blue Boar wrote:

ljknews wrote:

The environment with which I am most familiar is VMS, and tradition
is what guides secure interfaces.  Inner mode code _must_ probe any
arguments provided from an outer mode, probe the buffers specified
by descriptors provided, etc.

What do you do when you're handed a bad pointer?

Return SS$_ACCVIO.

So you put in an error handler that catches access ciolation before you try to use the pointer? OK, fair enough. What if the pointer points to memory you own, but not the right kind? I have always been under the impression that raw pointers could always cause you problems. I've assumed that a secure language would have to eliminate that as a type.


Reply via email to