Hello internals,
I get a segfault when starting apache with debug enabled in the php
build. I am using the latest 5_1 cvs, and apache 1.3
The backtrace i get in gdb is attached.
Is that likely to be caused with memory handling in an extension module?
It works fine in non-debug, but i am just try
If there are no (ultra last) objections, I'll roll 5.0.5 tomorrow morning
(.il/Europe time) and post it in the evening.
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I am an active member of the Spanish translation team.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
I spoke with my friend from doc-tr team ([EMAIL PROTECTED]) and he recomended
me
to request a cvs account. I'm very serious and determined about translation of
documentation to Turkish. My knowledge and experience about php is really good.
It was quite difficult to understand php doc in Eng
As you surely know, arrays are often badly initialized:
Wouldn't it be such a good thing to let the programmers know that this
is a bad habit, by throwing a +/- pedantic error ? I'm not sure which
type would suit for it, but I think its important enough to throw a
E_NOTICE.
I agree. I've alwa
I agree. I've always found it weird that no notice is thrown in this
situation. Still I discourage people to code like this.
Ron
"Etienne Kneuss" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> As you surely know, arrays are often badly initialized:
>
> // $array is undefi
Hi,
As you surely know, arrays are often badly initialized:
Wouldn't it be such a good thing to let the programmers know that this
is a bad habit, by throwing a +/- pedantic error ? I'm not sure which
type would suit for it, but I think its important enough to throw a
E_NOTICE.
It can be dange
