NGWS SDK Documentation  

This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!

Relationship to Type Safety

Type safety is usually discussed in terms of what it does, e.g. guaranteeing encapsulation between different objects, or in terms of what it prevents, e.g. memory corruption by writing where one shouldn’t. However, from the point of view of the Virtual Object System, type safety is about guaranteeing:

The Virtual Object System promotes type safety e.g. everything is typed. Type safety can be optionally enforced. The hard problem is determining if an implementation conforms to a typesafe declaration. Since the declarations are carried along as metadata with the compiled form of the program, a compiler from IL to native code (see Type Safety and Verification) can type-check the implementations. When coupled with code signing, the issue is then when to type-check and when to trust. For more information, see the security specifications.