Hey all,
This patch addresses the *printf() bug when dealing with exponents (%e).
See http://bugs.php.net/bug.php?id=46145 for more details.
The patch is large because there were a lot of unit tests written to expect
the wrong behavior, so I had to update them. I realize that there is the
possibility that we might decide to label this as a "won't fix", but I
figured I might as well put forth the effort :)
Ilia
Ilia Cheishvili wrote:
Hey all,
This patch addresses the *printf() bug when dealing with exponents
(%e). See http://bugs.php.net/bug.php?id=46145 for more details.The patch is large because there were a lot of unit tests written to
expect the wrong behavior, so I had to update them. I realize that
there is the possibility that we might decide to label this as a "won't
fix", but I figured I might as well put forth the effort :)
You can always make separate patches (preferred) for tests and code
changes. :)
When did it start misbehaving anyway? If it was like that all the time
-> wont fix, depending of course how long %e has existed..
--Jani
According to CVS, it has been that way since at least April of 2002. The
last time anyone touched it was a year and a half ago to clean up
whitespace.
So you're right, this very well may be a "won't fix". In that case, let's
mark it as such.
Ilia
On Thu, Sep 25, 2008 at 12:27 AM, Jani Taskinen jani.taskinen@sci.fiwrote:
Ilia Cheishvili wrote:
Hey all,
This patch addresses the *printf() bug when dealing with exponents (%e).
See http://bugs.php.net/bug.php?id=46145 for more details.The patch is large because there were a lot of unit tests written to
expect the wrong behavior, so I had to update them. I realize that there is
the possibility that we might decide to label this as a "won't fix", but I
figured I might as well put forth the effort :)You can always make separate patches (preferred) for tests and code
changes. :)When did it start misbehaving anyway? If it was like that all the time ->
wont fix, depending of course how long %e has existed..--Jani