Quote:
Originally Posted by Skyld
It is always a security issue because there will always be people who don't properly secure their code. Not only that but there will be people who will hide eval() scripts in order to abuse scripting once they have left a staff team or so.
|
I know... But -- Should the limitation be expressed by the current staff? I mean... People could potentially rescript the eval if they intended to do such... It doesn't pose any real security -- Only an articifial one.
But -- This is like:
PHP Code:
while ( i = getRow() ) ...;
It is there for a reason ( there is because too many people have done = instead of ==, and to remain consistent with GS1, GS2 loses the ability to )
HOWEVER... It diminishes the language unneededly.
Good programming practices should be honored and have their benefits. Bad programming should yield errors and unexpected results. It keeps the language universally understandable... and learning proper programming mechanics would be quite benificial for post-Graal work.