Re: Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only
| From: | Andrey Hristov | Date: | Thu, 09 Dec 2010 17:04:39 +0000 |
| Subject: | Re: Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50965@lists.php.net to get a copy of this message | ||
Reindl Harald wrote:
Am 09.12.2010 17:49, schrieb Andrey Hristov:I have been paid quite well for fixing other man's thrash because it just did not work. "Thus, one's thrash is another man's cash." But do we want this a normal job?sure, one's thrash is another mans cash.Stop this dumb style
I know very well which script is good anough with a simple hack and where i have to do a real application style and i do not like braindead ideas forcing me to get lost this decision There are so many reasons to write explicit "throw-away-code" and YOU DO NOT have to decide this for others Nobody forces you to use coding you do not like So please stop braindead forcing other peopleWho told you that I'm forced to write such code?
You probably got me wrong. The code will be broken and can be fixed. It's not like going line by line and checking whether everything will work. I'm tired of explaining this. AndreyWho taught you that globals mean clean design and non-reentrancy is cool and works?Who thaught you to decide what script from others has to be written in which way?Your writings today are idiotic "we should break existing code because we can"So why in the world would you like to kill them braindead without any valid reason, and "i do not like something" is not a valid reason because nobody forces you to use such things in your scriptsbecause my writings today are the legacy of tomorrow.