safe

Jonathan M Davis jmdavisProg at gmx.com
Mon Jun 13 08:43:54 PDT 2011


On 2011-06-13 08:02, sclytrack wrote:
> How safe is "safe D" to run on your computer as if it is a client
> application.
> 
> Let's say you want something like this.
> 
> 1) The source is compared to the local one on the current disk. If the
> remote version
> is newer the new version is downloaded.
> 
> 2) The source gets compiled and then executed in safe D but with only a
> subset of phobos that can not alter anything permanent on the disk. (as if
> it is a javascript client application).
> 
> Like a replacement for HTML5 and javascript.
> 
> ...or not suitable?
> 
> I'm going to eat now.

???? D is a systems language. You can do pretty much anything with it. SafeD 
is a subset of D which restricts certain types of operatons which are not 
necessarily memory safe, thereby avoiding certain types of bugs. When it says 
safe, it means _memory_ safe, and that's it. It doesn't really say much about 
what you can or can't do with the language. Sure, it's probably impossible to 
make a kernel with just SafeD, but D is not sitting in a sandbox like a web 
browser. It can do whatever it gets told to do. If anything, D is intended to 
be a replacement for C++, not HTML5 and javascript. It's a _systems_ language.

- Jonathan M Davis


More information about the Digitalmars-d mailing list