Talk:Rosetta Code/Run examples: Difference between revisions

→‎Overly ambitious: and dangerous
(→‎Overly ambitious: and dangerous)
Line 31:
The task currently says: "The program should verify that the tools needed to compile or run the solution are present before running it." But this is not possible, in the general case. For example, one task may need opengl installed, with the proper drivers for the hardware (and some platforms may have multiple sets of drivers installed only some of which are useful with the installed hardware), while another needs the user to be running a browser and yet another may require that the user be running a tty window and another may require a certain version of a certain library and another may require a certain virtual machine to be installed and configured properly... and these requirements will change both from task to task but also from implementation language to implementation language. --[[User:Rdm|Rdm]] 19:33, 5 December 2011 (UTC)
: quite right. good catch. when i wrote this i was only thinking of the executable needed to run the code or the compiler. that is, before the program attempts to run any command it should check if the command is available, or catch the error in some way with a message to the user. but come to think of it, it should probably catch any error and present it to the user, so the error can be fixed...--[[User:EMBee|eMBee]] 13:47, 8 December 2011 (UTC)
:: If you want to do something like this, you should require sandboxing, or at least remind users of risks. What if I snuck in stuff to the effect of "rm -rf /" right before some hapless one blindly pulls the code and runs it? It's an open wiki, and should by no means be considered trusted. --[[User:Ledrug|Ledrug]] 14:03, 8 December 2011 (UTC)
Anonymous user