On Sun, 5 Jan 2003, Leon Atkinson wrote:
> > Because this behavior is not documented
>
> For the record, it is documented:
> http://www.php.net/manual/en/function.strstr.php
>
> "If needle is not a string, it is converted to an integer and applied as the
> ordinal value of a character. "
Okay,
> Because this behavior is not documented
For the record, it is documented:
http://www.php.net/manual/en/function.strstr.php
"If needle is not a string, it is converted to an integer and applied as the
ordinal value of a character. "
And I'm sure it's worked this way for at least three years.
L
I mentioned a similar inconsistency of range() parameters in the past
and pointed out a possible BC breaking issue raised by your recent patch
on array.c in HEAD.
http://news.php.net/article.php?group=php.dev&article=91489
http://news.php.net/article.php?group=php.dev&article=92910
I meant no tri
On Sun, 5 Jan 2003, Ilia A. wrote:
> While converting the functions inside string.c to the new parameter parsing
> API and doing some general cleanup, I've come across an interesting
> 'feature'.
Ilia, there is a consensus that the new (slower) parameter
parsing is only supposed to be use
While converting the functions inside string.c to the new parameter parsing
API and doing some general cleanup, I've come across an interesting
'feature'.
Three string functions: stristr(), strstr() and strpos() have peculiar way of
handling non string values passed as 'needle'. Instead of conv
