mixin D code into D code

John Reimer terminal.node at gmail.com
Tue Feb 6 22:32:07 PST 2007


On Wed, 07 Feb 2007 07:53:20 +0200, Vladimir Panteleev wrote:

>>
>> Hmm... so is not possible that rdmd.exe (rdmd on linux) might commit the
>> same sort of security breech?  It's even packaged with the compiler?  Is
>> it safe?
> 
> rdmd is on the other side of the "line" which I described - its base purpose is to run code, while the compiler's purpose (unless explicitly specified by the user) is to manipulate code. If we are to continue thinking this way, why not eliminate the "executable" attribute on Unix filesystems and assume all files are executable? The user surely knows what is he doing. It's simply common safety practice.
> 
> Either way, allowing the compiler to run potentially dangerous code should at least be optional (however [my] common sense would say that it should be disallowed unless manually enabled). Imagine the problems this would cause with remote compiling systems, for example at ACM contests.
>


Good points.  Your argument make sense.

-JJR



More information about the Digitalmars-d mailing list