"Jehan-Guillaume (ioguix) de Rorthais" <ioguix@free.fr> wrote:
> and here is another test case where 8.3 is inconsistent with
> *himself* this time:
Sounds like an argument that the behavior *should* have changed in
8.4. We don't like to introduce behavioral changes which might
break something in a minor release, so I doubt we'd change that in
8.3; but on a major release like 8.4, this sort of fix is fair game.
So you found broken behavior in 8.3 which we can't fix without
risking breaking users' applications, and a fix implemented in 8.4
when such risk is acceptable?
Is there something else?
-Kevin
