On 25.01.2008 03:48, Joshua Abbott wrote:
Maintaining the documentation
Translating the documentation
Maintaining oci / mysql / postgresql extensions amongst others
It's usually good idea to start with sending patches, not with requesting an
account.
--
Wbr,
Antony Dovgal
--
PHP
quick work around for now..
base64_decode(json_decode(json_encode(base64_encode(ab\xE0\ something
Stanislav Malyshev wrote:
Hi!
Right now, if json_encode sees wrong UTF-8 data, it just cuts the string
in the middle, no error returned, no message produced. Example:
Hi!
Right now, if json_encode sees wrong UTF-8 data, it just cuts the string
in the middle, no error returned, no message produced. Example:
var_dump(json_encode(ab\xE0));
var_dump(json_encode(ab\xE0\));
Both strings get cut at ab. I think it's not a good idea to just
silently cut the data.
Should really theses functions discard the whole string for a single
incomplete sequence ?
I think since it is not possible to recover true content of the string,
it is ok to return failure value. Cutting it in random places or
ignoring problems doesn't seem a good idea - it might lead to
Hello Ditesh,
there are indeed. Both allow to compress the Phar entries. Personally I
prefer bz2 but as said earlier that only wroks with CVS code right now.
marcus
Friday, January 25, 2008, 4:48:57 PM, you wrote:
On Thu, 2008-01-24 at 09:14 -0800, chris# wrote:
I can't help but notice the
Hello chris,
there is no stability issue with gz and 5.2.6 will fix the last issue with
bz2/phar interaction. The actual reason for both being off is that they
reside in pecl and the assumption is that pecl modules are not present by
default. Simply add those two extensions and build again.
On Thu, 2008-01-24 at 09:14 -0800, chris# wrote:
I can't help but notice the defaults for gzip, and bzip is disabled.
I'm the port submitter/maintainer for pecl-phar. If there are good
reasons to have gzip/bzip2 support enabled by default, I'll be happy to
rectify the Makefile ASAP.
Cheers and
Pierre Joye wrote:
Hi Wez, Andi and all other persons behind this bad joke,
We clearly show that we are massively against a CLA in php core. Are
you suggesting that you want to release pdo2 only through PECL or some
non php.net repository?
Besides this little distribution problem, I find
Should really theses functions discard the whole string for a single
incomplete sequence ?
I think since it is not possible to recover true content of the string,
it is ok to return failure value. Cutting it in random places or
ignoring problems doesn't seem a good idea - it might lead to all
