Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: array_change_key_case()? key_exists()? From: Stig S. Bakken (ssb <email protected>)
Date: 11/12/01

Jeroen van Wolffelaar wrote:
>
> On Sun, 11 Nov 2001, Edin Kadribasic wrote:
>
> > Jeroen what you did was completely irresponsible. Without even starting a
> > discussion about whether a function is needed or not you take steps to
> > undocument them?!?
>
> Although I did 'undocument' them, I did so only __temporarily__
> (otherwise I'd have removed it really, not placed it inside a comment).
> The one and only reason to do so, is to prevent a BC problem in the case
> it turns out that this function will be changed/removed. Wether or not
> this will happen, is something I wanted to discuss -- the problem is
> simply that it'd be a lot harder to change function if it's documented,
> so I merely intended to postponed the documentation.
>
> As soon as - after discussion - it is decided that this function will
> stay, the comment marks should be removed. I'm only asking: let's
> discuss the function itself first.
>
> > I added array_change_key_case to address issues of making PEAR::DB truly
> > portable since different db backends have different conventions on returning
> > the case of column names. How else would you make an application that is
> > supposed to run on both Oracle in Postgres using asoc arrays as return
> > values? Or process the results of getallheaders() function.
>
> This function can easily be written in userland, using foreach.
> Of course, it's not as easy as this function, but after all, what this
> function does is nothing else as:

Jeroen, it is not your decision alone which functions go in and not in
PHP. You've stepped on enough toes here for a while, I will be revoking
your karma until we get this situation under control.

 - Stig