Hello
2009/1/28 Kenan R Sulayman :
> Why don't make the function return FALSE if parameter equals NULL ?
Well the $start parameter is required for substr(), so I don't see the
deal here? But with now initalizers being added in the manual by Jakub
its not much of a deal to use those values if you
Why don't make the function return FALSE if parameter equals NULL ?
--
(c) Kenan Sulayman
Freelance Designer and Programmer
Life's Live Poetry
2009/1/28 Paul Biggar
> On Wed, Jan 28, 2009 at 6:39 PM, Dan wrote:
> >>
> >> You're assumption is wrong then, NULL isn't treated as not passing a
>
On Wed, Jan 28, 2009 at 6:39 PM, Dan wrote:
>>
>> You're assumption is wrong then, NULL isn't treated as not passing a
>> value. The reason it worked with substr was by pure chance.
>>
>
> Out of interest, is there a reason that that is the case? Surely passing
> null would be best treated as the
>
> You're assumption is wrong then, NULL isn't treated as not passing a
> value. The reason it worked with substr was by pure chance.
>
Out of interest, is there a reason that that is the case? Surely passing
null would be best treated as the same as passing nothing?
Nathanael D. Noblet wrote:
> Peter Walther wrote:
> > it's only a bug if you always expect optional NULL parameters to be
>> ignored.
>
> Well that's the question I'm asking. I assumed optional parameters
> passed null should be ignored. If this isn't the behaviour php uses,
> then I'm good, but
Peter Walther wrote:
> it's only a bug if you always expect optional NULL parameters to be
ignored.
Well that's the question I'm asking. I assumed optional parameters
passed null should be ignored. If this isn't the behaviour php uses,
then I'm good, but I've used passing null to optional pa
On 27.01.2009 17:36, Nathanael D. Noblet wrote:
Johannes Schlüter wrote:
I know Ilia recently fixed a few functions that didn't ignore null
parameters, but it doesn't appear that substr() was one of them.
I guess that's part of the zend_parse_parameters changes. As we now use
the "s" modifier
On Wed, Jan 28, 2009 at 4:52 PM, Alpár Török wrote:
> 2009/1/28 Bipul Agarwal
>
> > Hi all,
> >
> > I have a search string which works just fine with php 4.4.9 and my local
> > host but some how its not working with php version 4.4.7.
> >
> > Search is for a Swedish name with special characters
2009/1/28 Bipul Agarwal
> Hi all,
>
> I have a search string which works just fine with php 4.4.9 and my local
> host but some how its not working with php version 4.4.7.
>
> Search is for a Swedish name with special characters like - åre - I am able
> to display these characters properly on the
Hello
2009/1/28 Bipul Agarwal :
> Hi all,
>
> I have a search string which works just fine with php 4.4.9 and my local
> host but some how its not working with php version 4.4.7.
Upgrade to PHP5 first, PHP4 is not supported anymore
> Thanks in advance,
> Bipul
>
>
> --
> PHP Internals - PHP Ru
Hi all,
I have a search string which works just fine with php 4.4.9 and my local
host but some how its not working with php version 4.4.7.
Search is for a Swedish name with special characters like - åre - I am able
to display these characters properly on the browser. the only problem is
with sear
Whitespace fixes are evil. Especially when NOT done in every branch like
they should. And then this happens.. thanks.
Marcus can fix it himself while checking every single file against every
branch in /Zend that they're in sync..
--Jani
shire wrote:
I came across a problem in PHP_5_3 and
12 matches
Mail list logo
