Re: Namespaces and \t, \r, \n, \0 etc.
| From: | Nate Gordon | Date: | Tue, 28 Oct 2008 21:56:56 +0000 |
| Subject: | Re: Namespaces and \t, \r, \n, \0 etc. | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-41538@lists.php.net to get a copy of this message | ||
On Tue, Oct 28, 2008 at 2:30 PM, Josh <josh.sickmate@gmail.com> wrote:
> What about just silently converting newline to '\n' and tab to '\t',
> etc. I mean if you cant put those characters in a string, who will
> notice? or better, just use a single-quoted string.
>
Random programmer here, but I really can't agree with silently converting
them. The less automagic foo that acts as a safety net, the better. Or do
we need to revisit gpc_magic_quotes? This theoretically shouldn't happen on
live code if it was tested at least once. But I am all for smart error
messages and single quotes. It will bite everyone at least once, and then
they will learn.
--
-Nathan Gordon
If the database server goes down and there is no code to hear it, does it
really go down?
<esc>:wq<CR>