Re: string_exec()
- Posted by katsmeow Mar 01, 2015
- 2467 views
Please try to provide examples that I have a vague chance of understanding
Can you explain what's so hard to understand about this?
So, assuming that division by zero is an NFI, when we execute
? 1/0
and hit the NFI, we rollback and replace it with
string_eval("? 1/0")
Well, presumably it is an NFI because it is inside a string_eval, so if we rollback (whatever that is) and replace it with a string_eval, it will cause an NFI which presumably we will rollback (whatever that is) and replace with a string_eval, which will cause an NFI which we can replace with a string_eval that causes an NFI that we replace with a string evalthatcausesanNFIthatwereplacewithastringevalthat...
What is the point?
Pete
No. What i was saying is the "string_eval(", is now a fatal error, you make it a non-fatal error. It is just one way to hook into runtime smarts like an interpreter should have. If it isn't a valid syntax, you could always progress to being fatal. Not that any error in a string should automatically be fatal.
If you have no other way of adding "string_eval()" to the keyword list, or other way of using runtime interpreter smarts to process "string_eval(", then maybe it's best to trip the interpreter via an NFI and to execute runtime code to simply strictly dynamically generate and replace the portion of the line containing "string_eval(blargboroo)" with whatever the interpreter would prefer to execute. Because really, when the code begins running, you have no clue what is in the string (or file, or console input, or table cell), so you cannot check anything in the string, which may indeed be null at the time.
Kat
