note 120154 deleted from function.eval by googleguy
| From: | googleguy@php.net | Date: | Fri, 24 Feb 2017 21:11:16 +0000 |
| Subject: | note 120154 deleted from function.eval by googleguy | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-208822@lists.php.net to get a copy of this message | ||
Note Submitter: clay_codes
----
eval() should be used for debugging.
I really don't understand why they are repeatedly expressing how "dangerous" it is,
and basically tell us not to use it... It's all just a little bit too much.
As coders, we should always try to use proper coding techniques and always protect our websites /
applications from SQL injections and other forms of hacking.
When creating the eval() function, the creators obviously had the compiler in mind. Why not add
something to escape the delimiters within the eval()? Or why not allow the use of curly brackets
like other functions? They could have just made it unusable / error out if there was a
"dangerous" apostrophe in it. Lol
I don't know. I just think this page makes it seem like we are all idiots incapable of using
the eval() statement properly. But I think as programmers we will be alright. We wont throw an
eval() directly into production just for laughs! We know to play around with it in development first
:)