At 09:52 PM 4/3/2001 +0100, James Moore wrote:
>Well, I dont think any of us really know how much damage it will cause. But
>on the other hand we can do this for years and just say well we mustn't
>break backwards compatibility and we will end up with somthing looking and
>behaving like perl. When
> James,
>
> You have to be aware that now PHP has such a big user base we need to be
> very careful in the changes we make especially when we can be pretty
> certain that it might burn quite a lot of people. We can break
> compatibility more easily when we have a major release (as from PHP 3 to
This is already configurable in php.ini using arg_separator and it
defaults to &. We should not be changing the default at this point.
-Rasmus
On Tue, 3 Apr 2001, Zeev Suraski wrote:
> My guess is that's the arg_separator fix. Jani?
>
>
> At 19:21 3/4/2001, Andi Gutmans wrote:
> >Anyone have
Hello James,
I agree, that standards it is good. You may certainly do such changes
which will break work of the previous programs, but then not in minor versions (4.0.x).
Probably you should release out 4.1.x, 4.2.x, because users have the right to hope,
that at change in minor versions not break
James,
You have to be aware that now PHP has such a big user base we need to be
very careful in the changes we make especially when we can be pretty
certain that it might burn quite a lot of people. We can break
compatibility more easily when we have a major release (as from PHP 3 to
PHP 4) b
> > Yes, that's true. I did ask (couple of times) before
> > I committed that patch. And yes, now both & and ; are
> > considered as arg separators.
> >
> > And I'd like to think that it's a feature than bug. ;)
>
> That would be true, if PHP would be some kind of reference
> implementati
At 10:01 PM 4/3/2001 +0200, Jani Taskinen wrote:
>On Tue, 3 Apr 2001, Zeev Suraski wrote:
>
> >My guess is that's the arg_separator fix. Jani?
>
>Yes, that's true. I did ask (couple of times) before
>I committed that patch. And yes, now both & and ; are
>considered as arg separators.
>
>And I'd l
On Tue, 3 Apr 2001, Sascha Schumann wrote:
> > Yes, that's true. I did ask (couple of times) before
> > I committed that patch. And yes, now both & and ; are
> > considered as arg separators.
> >
> > And I'd like to think that it's a feature than bug. ;)
>
> That would be true, if PHP would
> Yes, that's true. I did ask (couple of times) before
> I committed that patch. And yes, now both & and ; are
> considered as arg separators.
>
> And I'd like to think that it's a feature than bug. ;)
That would be true, if PHP would be some kind of reference
implementation. But we don'
On Tue, 3 Apr 2001, Zeev Suraski wrote:
>My guess is that's the arg_separator fix. Jani?
Yes, that's true. I did ask (couple of times) before
I committed that patch. And yes, now both & and ; are
considered as arg separators.
And I'd like to think that it's a feature than bug. ;)
This url exp
It might be valid but we might be breaking many people's sites.
I am not sure this is a very good idea.
Is it configurable via php.ini? We could keep the default the old behavior.
Andi
At 06:35 PM 4/3/2001 +0100, Anil Madhavapeddy wrote:
>It's the arg_separator changes isn't it? Both '&' and ';
At 19:21 03.04.2001 +0200, Andi Gutmans wrote:
>Anyone have an idea why this happens?
because someone wanted it to. it should be documented in the NEWS file.
but now php.ini as well as main.c shouldn't contain the ini entry anymore.
daniel
>Andi
>
>At 05:37 PM 4/3/2001 +0200, Andrew Sitnikov wr
It's the arg_separator changes isn't it? Both '&' and ';' are valid
delimiters in a URL, so the new 4.0.5 behaviour is actually the valid one, I
believe. Refer to the XHTML specification, or check out the bugs db for
this.
Anil
- Original Message -
From: "Andi Gutmans" <[EMAIL PROTECTE
13 matches
Mail list logo
