Re: multiselects and arrays

Why does it make more sense? Is there any advantage in using this over using foo[]? By changing this behavior, we're actually losing functionality, not adding any. Zeev At 18:53 10/5/2001, Adam Wright wrote:

Just from my point of view, I've got a lot of legacy code that relies on the fact that multiple inputs/query variables with the same name override one another. Changing this behaviour would break a lot of code methinks, but would probably make more sense in the longterm. adamw ----- Original Message ----- From: "Andrei Zmievski" <andrei@ispi.net> To: "Max Vysotskiy" <Maxim_Vysotskiy@ep.minsk.by> Cc: <php-dev@lists.php.net> Sent: Thursday, May 10, 2001 4:39 PM Subject: Re: [PHP-DEV] multiselects and arrays On Thu, 10 May 2001, Max Vysotskiy wrote:

Thanx But why not just to convert plain field names without [] to arrays?? Is there any reasons to not doing this?

That's been a pet peeve of mine as well. I think that if PHP sees multiple variables with the same name in POST data, it should make an array out of them.. -Andrei * All of the above is my opinion, unless specified otherwise. * -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/