safety model in D

[jpf]

Andrei Alexandrescu wrote:
> jpf wrote:
>> You may want to have a look at the CoreCLR security model (that's used
>> by silverlight / moonlight). It's quite similar to what you've proposed.
>> http://www.mono-project.com/Moonlight2CoreCLR#Security_levels
> 
> I don't have much time right now, but here's what a cursory look reveals:
> 
> ====================
>  Security levels
> 
> The CoreCLR security model divide all code into three distinct levels:
> transparent, safe-critical and critical. This model is much simpler to
> understand (and implement) than CAS (e.g. no stack-walk). Only a few
> rules can describe much of it.
> ====================
> 
> The keywords "security" and "stack-walk" give it away that this is a
> matter of software security, not language safety. These are quite
> different.

What i wanted to refer to are the levels "Transparent", "Critical" and
"Safe Critical", which work exactly as "safe", "system" and "Yeah, I do
unsafe stuff inside, but safe modules can call me no problem". The
implementation and use case might be different, but the meaning is the
same. There's nothing unique in the .net implementation, I just though
you may want to have a look at how others solved a similiar problem.