That is a test that is involved in the iconv's transilteration
feature, the behavior of which may vary by the platform you use. I
guess we don't actually need to test it then.
Moriyoshi
On Tue, Jul 28, 2009 at 12:27 PM, Rasmus Lerdorfras...@lerdorf.com wrote:
Moriyoshi, or someone who knows
Incorporating the changes and merges across the branches into one
commit under a sparse-layouted local copy doesn't do the book-keeping
against svn:mergeinfo. That's why I suppose it is not a good idea.
Moriyoshi
On Tue, Jul 28, 2009 at 7:44 AM, Gwynne Raskindgwy...@darkrainfall.org wrote:
On
On Sat, Jul 4, 2009 at 18:32, Sandro Tosimo...@debian.org wrote:
Hi all,
On Sat, Jul 4, 2009 at 18:20, Sean Coatess...@caedmon.net wrote:
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net
bts
that
I set up a RFC page for this in wiki.php.net. Here it goes:
http://wiki.php.net/rfc/altmbstring
Moriyoshi
2009/7/26 Moriyoshi Koizumi m...@mozo.jp:
Hi there,
I almost finished an alternative implementation of mbstring that uses
ICU instead of the exotic libmbfl in hope of replacing the
Moriyoshi Koizumi wrote:
Incorporating the changes and merges across the branches into one
commit under a sparse-layouted local copy doesn't do the book-keeping
against svn:mergeinfo. That's why I suppose it is not a good idea.
I don't think a merge will work the way we use branches though.
*bump*
Dmitry, did you have a chance to review this patch yet?
- David
On 22.06.2009, at 15:21, David Zülke wrote:
Hi folks,
attached is a patch (with the respective test cases) that implements
DateTime marshalling from and to xsd:dateTime in ext/soap as
requested in
On 28.07.2009, at 01:38, Takeshi Abe wrote:
Hi,
On Mon, 27 Jul 2009 18:44:20 -0400, Gwynne Raskind gwy...@darkrainfall.org
wrote:
README.SVN-RULES says
1. All changes should first go to trunk and then get merged from
trunk
(aka MFH'ed) to all other relevant branches.
which I've
Hi David,
I took only a quick look, but I like the patch.
In case it doesn't break any tests, it should be committed at least into
HEAD. I agree to commit it into 5.3 too, but RMs take the final decision.
The only thing I didn't understood - why win32/php_stdint.h is needed.
Thanks. Dmitry.
On 28.07.2009, at 13:32, Dmitry Stogov wrote:
Hi David,
I took only a quick look, but I like the patch.
In case it doesn't break any tests, it should be committed at least
into
HEAD. I agree to commit it into 5.3 too, but RMs take the final
decision.
The only thing I didn't understood -
David Zülke wrote:
On 28.07.2009, at 13:32, Dmitry Stogov wrote:
Hi David,
I took only a quick look, but I like the patch.
In case it doesn't break any tests, it should be committed at least into
HEAD. I agree to commit it into 5.3 too, but RMs take the final decision.
The only thing I
On Wed, 15 Jul 2009, Joe Orton wrote:
Derick, do you make available the scripts used to generate timezonedb.h?
They're at http://cvs.xdebug.org/cgi-bin/viewvc.cgi/timelib/zones/
Are you using the location co-ordinates from zone.tab in the Olson
database?
Yes, but there was a tiny bug with
Hi,
I'm wondering where the Zend/zend_float.h include file is used. I'm
interested in because I'm checking the behaviour variation between PHP4
and PHP5 (*), and floating point management seems to be fixed for all
platforms in an early version of PHP5 (revision r270301).
By the way,
Gwynne Raskind wrote:
On Jul 27, 2009, at 6:31 PM, Takeshi Abe wrote:
Just to be sure, is there any consensus on this? I thought I should
use svn merge.
README.SVN-RULES says
1. All changes should first go to trunk and then get merged from trunk
(aka MFH'ed) to all other relevant
Hi
2009/7/28 Lupus Michaelis mickael+...@lupusmic.org:
Hi,
I'm wondering where the Zend/zend_float.h include file is used. I'm
interested in because I'm checking the behaviour variation between PHP4 and
PHP5 (*), and floating point management seems to be fixed for all platforms
in an
Dmitry Stogov wrote:
David Zülke wrote:
On 28.07.2009, at 13:32, Dmitry Stogov wrote:
Hi David,
I took only a quick look, but I like the patch.
In case it doesn't break any tests, it should be committed at least into
HEAD. I agree to commit it into 5.3 too, but RMs take the final decision.
15 matches
Mail list logo
