Re: Re: ; arg seperator

Shouldn't the solution be that the parser uses '&' *and* arg_separator when arg_separotor is not '&'? In that way the default behaviour of php is unchanged. Edin ----- Original Message ----- From: Edin Kadribasic <edink@proventum.net> To: Jani Taskinen <sniper@iki.fi> Cc: PHP Developer List <php-dev@lists.php.net>; PHP Quality Assurance <php-qa@lists.php.net> Sent: Wednesday, April 04, 2001 12:14 AM Subject: Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: ; arg seperator > > >> Which reminds me: If arg_separator is used like it was before my patch > > >> and you set it to e.g. ';' and then have a form which method > > >> is GET..well, it won't work. there would be one variable > > >> holding all the info. > > > > > >Urls that are the result of a submitted form are generated by the browser > > >and not php, and I don't know of a browser that will use anything other > that > > >'&' for that. > > > > Exactly. And that's why if you change the arg_separator to ";" > > those forms didn't work (before my patch). > > > > I actually didn't test it though so I'm not 100% sure. > > Could someone check it out with 4.0.4pl1? > > You are right. The following php script: > > <?php > print "a=$a<br>b=$b<br>"; > ?> > <form> > <input type="text" name="a" value="1"><br> > <input type="text" name="b" value="1"><br> > <input type="submit"> > </form> > > with arg_separator set to ";" in php.ini produces > > a=1&b=2 > b= > > It is clear that documentation in php.ini is wrong, arg_separator is not > only used for generation but also for parsing of arguments (4.0.4pl1).