Restrict access to "critical" functions

Timon Gehr timon.gehr at
Wed Dec 14 04:48:08 PST 2011

On 12/14/2011 01:28 PM, Kagamin wrote:
>> Goal would be to have a possibility to compile and let run code from
>> random people (some of them perhaps evil minded), watch over the
>> processes and kill them, if they take too long or use up too much memory.
> I believe this is what SafeD is for.

SafeD eliminates the possibility of memory corruption, it does not 
prevent the program from messing with the system.

More information about the Digitalmars-d-learn mailing list