On 10/21/07, 131 <[EMAIL PROTECTED]> wrote:
> It's not always a structural issue :/
It is
> I'm sure non defined string interpretation is a bad thing
it is definitely a bad thing, but it is a documented bad thing and I
believe there are still some scripts which rely on this
> I'm not a php core w
It's not always a structural issue :/
I'm sure non defined string interpretation is a bad thing
I'm not a php core writter, but it have to be, even a little, more
complicated to use undefined constants as there "string" value, than as
"null"
Maybe i'm the only one thinking that way.
I'll try to
news.php.net wrote:
I might have a define("DEBUG",$_SERVER["REMOTE_ADDR"]=="myip"); included -
on not
Just make sure you always set DEBUG, shouldn't be too hard if your code
has any structure ;-)
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://w
""Alexey Zakhlestin"" <[EMAIL PROTECTED]> a écrit dans le message de news:
[EMAIL PROTECTED]
> and what's wrong with the following syntax?
>
> if(defined('DEBUG')) print_r($_SESSION);
I might have a define("DEBUG",$_SERVER["REMOTE_ADDR"]=="myip"); included -
on not
I know defined exists but, m
and what's wrong with the following syntax?
if(defined('DEBUG')) print_r($_SESSION);
I don't think there's a need to change anything here…
On 10/19/07, news.php.net <[EMAIL PROTECTED]> wrote:
> I was wondering if someone already think about modifying the actual behavior
> of undefined constants
