On Wed, January 23, 2008 6:58 pm, Andrei Zmievski wrote:
> It seems we're only talking about literals here. What about the rest
> of
> the places where unicode.semantics switch matters right now, like
> streams (works in binary or unicode mode), incoming request decoding,
> etc? It would be a shame
Maintaining the documentation
Translating the documentation
Maintaining oci / mysql / postgresql extensions amongst others
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
top-posting because it's already messed up...
You will need a massive education effort in PHP 6 to start using
b"foo" for all non-UTF-8 strings because PHP 7 default will be UTF-8.
Or, yes, you will be in the same boat for PHP 7.
Or you can just start the education effort now and not release PHP
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 rather sad that you
choosed
[Note: replies set to [EMAIL PROTECTED]; let's keep the discussion on
that list rather than cluttering up [EMAIL PROTECTED]
Hi all,
Please accept our apologies that it's taken so much time to make these
clarifications on some of the discussions regarding PDO 2.
It became apparent over the past
On Wed, 23 Jan 2008 14:56:32 -0600, Greg Beaver <[EMAIL PROTECTED]> wrote:
> Sam Barrow wrote:
>> PHP has ZIP, GZip, and BZ2 support, but nothing for tar archives. Is
>> anyone interested in working on a tar extension?
>
> FYI, pecl/phar has full tar support plus tar.gz/tar.bz in the
> soon-to-be
Hi,
The htmlspecialchars and htmlentities functions since version 5.2.5 return an
empty string when the input contains at least a single invalid or incomplete
unicode sequence.
What I understood is that this change was made to avoid reading more chars in
the buffer than it actually contained.
