Re: Why is the default value for arg_separator.output '&'?

On Tue, April 19, 2005 7:45 pm, Roger B.A. Klorese said: > Richard Lynch wrote: > >>Why in the world should we be forced to follow your narrow-minded >>so-called "standard"? :-) >> >> > > Hint: smileys indicate that you're joking. If you're joking, I don't > get what's humorous -- please explain. If you're making a serious point > but trying to have the rhetorical equivalent of "no offense, but..." you > should probably know that any time someone says "no offense, but..." > they really mean to offend but get off scot-free. Okay, I meant to offend. :-) Happy? :-) :-) :-) >>Furthermore, the & as separator pre-dates & by *years* and billions >> of >>lines of code could be affected by altering the default. >>So, really, Backwards Compatibility alone makes this a no-brainer default >>value of: & >> > So default behaviors should never change?! Absurd. you should be > notified that they are changed, and should have a mechanism to configure > for the previous behavior... but they have to be allowed to change as > standards do. Please feel free to take this up with the Developers on PHP-Dev or PHP-Internals or whatever and argue the issue with them. But if it's going to break a billion scripts, it's probably not gonna happen to follow a "standard" that isn't the only game in town. XHTML is not ubiquitous. [shrug] Since there are still browsers in use that will choke on & in the URL, last time I checked, you're pretty much fighting for a lost cause, as far as I'm concerned. Good Luck! -- Like Music? http://l-i-e.com/artists.htm