December 15, 2011 Re: Restrict access to "critical" functions | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jonathan M Davis | On 12/15/2011 06:04 PM, Jonathan M Davis wrote: > On Thursday, December 15, 2011 13:57:21 deadalnix wrote: >> Even haskell has non pure functions (IO monad for exemple). > > Actually, Haskell is a 100% purely functional language. Not entirely. For example: http://users.skynet.be/jyp/html/base/System-IO-Unsafe.html > Monads are completely > pure. They're _how_ Haskell manages to be pure with I/O, when every functional > language before them had had to be impure with regards to I/O. > > - Jonathan M Davis |
December 18, 2011 Re: Restrict access to "critical" functions | ||||
---|---|---|---|---|
| ||||
Posted in reply to mta`chrono | Yep. Useful google dork: sandbox.
On 14.12.2011 19:55, mta`chrono wrote:
> Maybe you should use a VM to run your restricted applications. Or have a look a chroot, dchroot or schroot, to setup such stuff. The Programming Language will not help you in this case!
|
December 18, 2011 Re: Restrict access to "critical" functions | ||||
---|---|---|---|---|
| ||||
Posted in reply to Bystroushaak | Bystroushaak wrote:
> Useful google dork: sandbox.
nice: safeD -> sandbox -> VirtualBox
Make a virtual machine an integral part of the compiler :-)
-manfred
|
December 21, 2011 Re: Restrict access to "critical" functions | ||||
---|---|---|---|---|
| ||||
Posted in reply to Andrew Wiley | > Honestly, I don't think what you're looking for is possible in *any*
> statically compiled systems language.
NaCl does feature some code verification.
|
Copyright © 1999-2021 by the D Language Foundation