Re: [PHP-DEV] proposal for change the argument of parse_str/mb_parse_str

2011-09-11 Thread Reindl Harald
Am 11.09.2011 06:31, schrieb Rui Hirokawa: > Hello, > > I think the second argument of parse_str/mb_parse_str > should be changed from optional to mandatory. > parse_str(string encoded_string [, array result]) > -> parse_str(string encoded_string , array result) no because there is no reason an

Re: [PHP-DEV] proposal for change the argument of parse_str/mb_parse_str

2011-09-11 Thread Stas Malyshev
Hi! On 9/10/11 9:31 PM, Rui Hirokawa wrote: I think the second argument of parse_str/mb_parse_str should be changed from optional to mandatory. This would create BC problems. You can mess up you code with any function, I do not think it warrants BC break. -- Stanislav Malyshev, Software Arch

[PHP-DEV] proposal for change the argument of parse_str/mb_parse_str

2011-09-10 Thread Rui Hirokawa
Hello, I think the second argument of parse_str/mb_parse_str should be changed from optional to mandatory. parse_str(string encoded_string [, array result]) -> parse_str(string encoded_string , array result) It is to reduce the risk of vulnerability, and it has neary same risk as register_globa