On Tue, 7 Oct 2003, Stefan Walk wrote:
> On Tue, Oct 07, 2003 at 02:40:19AM +0300, Jani Taskinen wrote:
> >
> > Passing array_merge*() anything else but arrays is undocumented.
> > These functions were meant to be used on arrays and this change
> > (very, VERY minor change, if I may say so) just "fixes" this.
> >
> > RTFM. :)
> >
> > --Jani
>
> Do you want me to fix the str* functions, since it seems those are
> accepting numbers?
Trying being sarcastic? Tip: it doesn't work on a mailinglist to reach
some goal.
> What is the problem with array_* functions casting implicitely? The vast
> majority of php functions does implicit casting, array_splice does it,
> everyone is used to it, PHP is known for it... why go the other way now?
Because it's plain wrong? Array functions should not cast any scalar to
an array, not even array_splace IMO because a scalar is NOT a non-scalar
as an array or object.
> Btw, this `very, VERY minor change' broke pear.
That has nothing to do with this change, just by a bad design choice.
Once more the description in the manual:
array_merge() merges the elements of two or more arrays together
so that the values of one are appended to the end of the
previous one. It returns the resulting array.
regards,
Derick
--
"Interpreting what the GPL actually means is a job best left to those
that read the future by examining animal entrails."
-------------------------------------------------------------------------
Derick Rethans http://derickrethans.nl/
International PHP Magazine http://php-mag.net/
-------------------------------------------------------------------------
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
