Re: Removing track_vars?

I don't think people rely on this, and if they do, I think that's a downwards compatibility issue we should face. I think having them around reliably is more important than having some non-standard checks work (we never advertised whether $HTTP_FOO_VARS[] gets defined as an empty array or not). Zeev At 23:32 05/09/2000, André Langhorst wrote:

I didn't understand your example and reasoning; I'm against that in general, they should be very 'sound' variables, that are always available. If they're empty - they'll be an empty array (which evaluates to false, FWIW).

sure, sentence was hard to parse, forgot to mention 'isset()'. it *could* be that people rely on the existance of some $HTTP_GET_VARS or POST_VARS array to start some logic, as follows: 1) variables_order=pc 2) script with some logic, if (isset($HTTP_GET_VARS)) print_out_do_not_try_to_hack_message(); well and if you´re creating these arrays although they´re not listed in variables_order, you´ll break backwards compatibilty in those (I think very rare) cases perhaps you already implemented it this way (to take care of variable_order), had no success buildind CVS, will try again andré

-- Zeev Suraski <zeev@zend.com> http://www.zend.com/