On 2/11/2023 2:46 am, Derick Rethans wrote:
Hi,
I have just opened voting on the RFC to unbundle imap, pspell, and
oracle integrations.
:)
--
https://twitter.com/ghrd
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
On 27/9/2023 11:27 pm, Derick Rethans wrote:
Hi,
after the initial introduction, here is the formal RFC to unbundle the
imap, pspell, and oci8 extensions and move them to PECL, for PHP 8.4.
https://wiki.php.net/rfc/unbundle_imap_pspell_oci8
cheers,
Derick
Hi Derick,
A small point: the
On 12/7/21 5:49 pm, Nikita Popov wrote:
On Wed, Jun 30, 2021 at 11:32 AM Nikita Popov wrote:
Hi internals,
I have opened voting on
On 20/11/20 1:50 am, Sara Golemon wrote:
I've just cut the release branch for PHP-8.0.0 final which will be released
in one week on 26 Nov. Minor bug fixes can continue to be merged via the
PHP-8.0 branch for inclusion in 8.0.1, but 8.0.0 will be precisely what
8.0.0RC5 contained unless
On 18/6/18 5:43 am, Stanislav Malyshev wrote:
Hi!
I would like to open the vote for the RFC about cleaning up the
unmaintained extensions:
https://wiki.php.net/rfc/umaintained_extensions
The vote ends 2018-06-26 23:59 PDT.
I have added some discussion about active maintainers and abandonment
On 2/11/17 8:58 am, Stanislav Malyshev wrote:
Hi!
Voting has now started on the flexible heredoc and nowdoc syntaxes RFC[1].
Voting will be open for 2 weeks (until November 15th).
Something I am missing here. RFC is talking about removing indents from
heredoc text, but the vote says
On 24/10/17 8:27 pm, Thomas Punt wrote:
Hi Christopher,
> I like the added flexibility in placement of the end token, but I think requiring only tabs or spaces, and stripping whitespace from all
{here|now}doc
> lines is error prone and adds unnecessary complexity.
I agree that the
On 13/10/17 8:40 pm, Thomas Punt wrote:
Morning internals,
I'd like to propose an RFC to make the heredoc and nowdoc syntaxes more
flexible[1]. Any thoughts?
Thanks,
Tom
[1]: https://wiki.php.net/rfc/flexible_heredoc_nowdoc_syntaxes
I like the added flexibility in placement of the
On 20/7/17 10:31 am, Anatol Belski wrote:
Hi Chris,
-Original Message-
From: Christopher Jones [mailto:christopher.jo...@oracle.com]
Sent: Thursday, July 20, 2017 2:11 AM
To: Anatol Belski <a...@php.net>; php-...@lists.php.net; Tianfang Yang
<tianfang.y...@oracle.com>
On 26/6/17 4:43 pm, Joe Watkins wrote:
Morning,
I also voted no for similar reasons to Anatol.
This is not really a thing that needs a vote, this is a thing that requires
the handful of people who are actually able to document ZE to spend
considerable time doing so. In addition it requires a
On 22/6/17 1:43 am, Fleshgrinder wrote:
On 6/21/2017 5:38 PM, Nikita Popov wrote:
Can you please clarify where functions that are declared in a header and
defined in a source file should be documented? I believe the usual
recommendation is to document in the source file, because it's closer
On 17/6/17 5:53 pm, Fleshgrinder wrote:
Hi!
I started voting on the Doxygen RFC:
https://wiki.php.net/rfc/doxygen
Did I miss seeing when the vote ends?
Chris
--
http://twitter.com/ghrd
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
On 15/6/17 10:34 pm, Johannes Schlüter wrote:
On Do, 2017-06-15 at 11:06 +0200, Nikita Popov wrote:
On Tue, Jun 13, 2017 at 8:23 AM, Remi Collet
wrote:
Hi,
All extensions in php-src are PHP 3.01 Licensed
(libs may, of course, have different license)
Is there any
On 29/3/17 2:11 am, Sara Golemon wrote:
On Tue, Mar 28, 2017 at 9:56 AM, Joe Watkins wrote:
With the first alpha of 7.2 due in early June, we think it's time to start
the process of finding and electing release managers for the next minor
release of PHP.
We are looking
On 1/3/17 12:58 am, Adam Baratz wrote:
Merging responses here...
Are PARAM_STR_UNICODE, ATTR_UNICODE_STRINGS and PARAM_STR_ASCII the most
appropriate names?
Good point. Maybe instead:
* PDO::PARAM_STR_NATL
* PDO::ATTR_NATL_STRINGS
* PDO::PARAM_STR_CHAR
How does this
On 26/2/17 9:07 am, Marco Pivetta wrote:
Hi Adam
On Fri, Feb 24, 2017 at 2:28 PM, Adam Baratz wrote:
Based on some pain points with my team and things I've heard from others,
I created an RFC to handle "national" character sets for emulated
prepared
statements:
On 5/09/2016 8:13 PM, Derick Rethans wrote:
On Fri, 2 Sep 2016, Davey Shafik wrote:
I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and
remove in 8.0), as well as add composer/pickle (optional in 7.2,
default in 7.3+) in their place.
On 15/08/2016 6:17 PM, Kalle Sommer Nielsen wrote:
Hi Stas
2016-08-15 7:53 GMT+02:00 Stanislav Malyshev :
Hi!
I'd like to propose an RFC to deal with extensions that currently have
no maintainer:
https://wiki.php.net/rfc/umaintained_extensions
pdo_oci
I have heard
On 28/06/2016 1:17 AM, Aaron Piotrowski wrote:
Hello,
Voting has opened on the RFC to change most conditions in extensions that raise
E_ERROR or E_RECOVERABLE_ERROR to throw an instance of Error instead.
RFC: https://wiki.php.net/rfc/throw_error_in_extensions
Not sure if this helps, but perhaps something like this:
# gmake Makefile fragment to clean a file of its carriage returns.
# Carriage returns drive the Studio compiler crazy.
cleancr = $(GSED) -i -e 's/\r//g' $(1) ;
Chris
On 26/01/2016 3:05 AM, Ross, Christine wrote:
Hi
Thank you for
On 9/11/2015 6:15 am, Anatol Belski wrote:
Hi,
After doing the last evaluations in the RMs circle before going for 7.0.0
RTM preparations, we came to the conclusion that the current state does not
look reasonable to be packaged as the final release.
The RCs before RC6 was looking acceptable,
On 9/11/2015 7:01 am, Peter Cowburn wrote:
Hi folks,
It's that time of year again. If you are using our PhpStorm license, you've
probably been prompted about it expiring in December. JetBrains have
kindly offered their open source license to us again, and as usual all
details are on the
On 19/08/2015 9:17 pm, Bob Weinand wrote:
Am 19.08.2015 um 01:46 schrieb Christopher Jones christopher.jo...@oracle.com:
On 12/08/2015 11:31 pm, Ferenc Kovacs wrote:
On Wed, Aug 12, 2015 at 1:55 PM, Christopher Jones christopher.jo...@oracle.com
mailto:christopher.jo...@oracle.com wrote
On 12/08/2015 11:31 pm, Ferenc Kovacs wrote:
On Wed, Aug 12, 2015 at 1:55 PM, Christopher Jones christopher.jo...@oracle.com
mailto:christopher.jo...@oracle.com wrote:
Bob,
Is the ext/phpdbg_webhelper sym link really needed ? If so, can you add it
to .gitignore.
Thank you
Bob,
Is the ext/phpdbg_webhelper sym link really needed ? If so, can you add it to
.gitignore.
Thank you,
Chris
--
http://twitter.com/ghrd
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 30/07/2015 11:12 pm, Niklas Keller wrote:
2015-07-30 14:42 GMT+02:00 Andone, Bogdan bogdan.and...@intel.com:
-Original Message-
From: Niklas Keller [mailto:m...@kelunik.com]
Sent: Thursday, July 30, 2015 1:47 PM
To: Pierre Joye
Cc: lp_benchmark_robot; PHP internals;
We are looking at reordering the PDO statement-free dtors to fix a
resource leak in PDO_OCI. Let me know if this will affect other
drivers.
Chris
*** pdo_stmt.c.orig 2015-07-15 09:56:18.986187123 -0700
--- pdo_stmt.c 2015-07-15 09:57:22.292453715 -0700
***
*** 2300,2305
On 4/22/15 6:39 AM, Stelian Mocanita wrote:
The removal of pdo_oci had been suggested as part of the Removal of dead or not yet
PHP7 ported SAPIs and extensions RFC, but there has been
feedback from Christopher Jones, that the extension will be supported by
Oracle.[1] [1]
https
RFC, but there has
been feedback from Christopher Jones, that the extension will be
supported by Oracle.[1]
[1]
https://wiki.php.net/rfc/removal_of_dead_sapis_and_exts#extpdo_oci_and_extoci8
Thanks for the info. Having Oracle supporting the extensions would
On 4/22/15 2:40 AM, Stelian Mocanita wrote:
Hello internals,
I would like to ask what on your thoughts on removing the Oracle drive for
PDO from the documentation (http://us1.php.net/manual/en/ref.pdo-oci.php)
at least since it's been experimental for a long time now, and it has long
standing
On 4/14/15 9:58 PM, Pierre Joye wrote:
On Wed, Apr 15, 2015 at 10:51 AM, christopher jones
christopher.jo...@oracle.com wrote:
On 4/14/15 7:21 PM, Pierre Joye wrote:
hi,
We tried that many times but we fail to handle the version of bundled
extensions.
Along with some installer work
On 4/14/15 7:21 PM, Pierre Joye wrote:
hi,
We tried that many times but we fail to handle the version of bundled
extensions.
Along with some installer work and other integration (projects
dependencies management, composer or other), we need to find a way to
get rid of this problem.
What do
On 3/4/15 9:03 AM, Rowan Collins wrote:
On Wed, Mar 4, 2015 at 10:24 AM Rasmus Lerdorf ras...@lerdorf.com wrote:
Yasuo, please stop. This isn't going to happen. Changing strlen() to str_len()
is just ridiculous. -Rasmus
Trevor Suarez wrote on 04/03/2015 15:33:
... well that's a
On 1/10/15 9:03 AM, François Laupretre wrote:
To summarize, I started with a rather simple feature request and was
then pushed by external wishes.
See #13 at
https://blogs.oracle.com/opal/entry/the_mysterious_php_rfc_process
Take advice on board but make sure your feature doesn't end up
On 10/16/14, 8:47 AM, Rasmus Lerdorf wrote:
On 10/16/2014 04:27 AM, Ferenc Kovacs wrote:
On Fri, Jun 15, 2012 at 3:01 AM, Anthony Ferrara ircmax...@gmail.com
wrote:
Hello all,
I raised this topic on list over a year ago (
http://marc.info/?l=php-internalsm=130417646507744w=2 ). It was
On 9/16/14, 9:11 AM, Jorge F. Hernandez wrote:
On 9/16/2014 11:14 AM, Anatol Belski wrote:
I made a build from the current revision
http://windows.php.net/downloads/snaps/ostc/master-f469dc74/ so anyone
curious can easy snuffle :) It contains all the currently ported exts +
debug symbols,
Fine for OCI8 and PDO_OCI. I'll let you know when to re-enable.
On Aug 31, 2014 7:43 AM, Nuno Lopes nlop...@php.net wrote:
Hi,
I've disabled the following extensions from the build of PHP_HEAD at the
gcov.php.net server:
- oci8
- pdo_oci
- sybase_ct
- litespeed SAPI
These
On 8/22/14, 5:11 AM, Pierre Joye wrote:
On Fri, Aug 22, 2014 at 1:28 PM, Bob Weinand bobw...@hotmail.com wrote:
Yes, please. We're all in favor of the 64 bit implementation, but definitely
not on
the naming. I think it was a big mistake to not separate the naming and
implementation votes
On 8/21/14, 10:23 AM, Dmitry Stogov wrote:
Hi,
Thanks to Anatol and Pierre the 64-bit patch is ready
https://github.com/weltling/php-src
I made quick code review and don't see any technical problems now.
The performance and memory consumption difference is negligible. see
On 8/21/14, 11:09 AM, Levi Morrison wrote:
Every time we break BC — in either of the ways Derick said — we narrow
the subset of PHP 5 and PHP 7 that's available to people writing PHP
code that has to work on both. If we narrow it too far, it'll be too
unexpressive, or too hard to use, or just
On 10/31/13 4:12 PM, Stas Malyshev wrote:
Hi!
Final comments anyone, before I commit next week?
It looks strange that we have to hardcode so many mimetypes in the code,
and doesn't sound a scalable solution. Can't we make it use data from
fileinfo or some other customizeable table so we
I'm planning on adding some MIME type to the CLI web server.
For PHP 5.5.5 CLI web server I added the .pdf MIME type. I was using
the webserver for a conference exhibition hall demo and needed to
present a PDF.
Some other multi-media types could be useful in future situations, and
in general.
On 10/17/2013 10:19 PM, Ferenc Kovacs wrote:
On Thu, Oct 17, 2013 at 5:29 PM, Pierre Joye pierre@gmail.com wrote:
On Thu, Oct 17, 2013 at 7:56 AM, Michael Wallner m...@php.net wrote:
On 17 October 2013 16:29, Felipe Pena felipe...@gmail.com wrote:
+1 for Ferenc Kovacs. (is it a
On 10/02/2013 10:26 AM, Nikita Popov wrote:
Hi internals!
I'd like to change our double-to-string casting behavior to be
locale-independent and would appreciate some opinions as to whether you
consider this feasible.
So, my suggestion is to change the (string) cast to always use . as the
On 9/26/13 7:22 AM, Lior Kaplan wrote:
Hi,
In Debian we build PHP for GNU/Hurd system, which need some minor fixes
available here:
http://anonscm.debian.org/gitweb/?p=pkg-php/php.git;a=blob;f=debian/patches/116-posixness_fix.patch
(per the guidelines here:
On 9/5/13 3:32 AM, Pierre Joye wrote:
On Thu, Sep 5, 2013 at 11:34 AM, Nikita Popov nikita@gmail.com wrote:
On Thu, Sep 5, 2013 at 10:51 AM, Pierre Joye pierre@gmail.com wrote:
On Thu, Sep 5, 2013 at 10:23 AM, Sebastian Krebs krebs@gmail.com
wrote:
That being said, there is
On 8/5/13 8:12 AM, Jan Ehrhardt wrote:
Julien Pauli in php.internals (Fri, 2 Aug 2013 10:05:00 +0200):
Please test the release carefully and report any bugs.
What is the best way to report things that are so small that opening an
issue would be overkill?
I have got some tiny remarks:
-
On 07/07/2013 07:55 AM, Sebastian Bergmann wrote:
On 07/07/2013 04:31 PM, Sebastian Bergmann wrote:
Currently --enable-debug sets -O0. I think it would make sense to
use -Og instead when GCC = 4.8.0 is used.
https://gist.github.com/sebastianbergmann/5943708 is an attempt to
implement
On 07/03/2013 07:12 AM, Anthony Ferrara wrote:
Then, I defined a series of new types:
#ifdef ZEND_USE_LEGACY_STRING_TYPES
Due to a problem with zend_parse_parameters, I added two new identifiers: S
and P. They act just like s and p, except that they return zend_str_size
instead of int.
On 06/27/2013 09:33 AM, Ralf Lang wrote:
Anyway, I have built a version of the patch (using unsigned long instead
of signed long as the original did) against old php 5.3.8 and currently
a test is running with a 4.7 GiB DVD Image. If it works well, I will
submit the patch and attach it to the
On 05/09/2013 05:02 AM, Pierre Schmitz wrote:
Hi,
I am testing PHP 5.5 atm and how we can package it for Arch Linux and
provide an upgrade path for users. The RC1 looks pretty solid so far.
As the new opcache does not provide a user cache to store custom
variables, I would be glad if you
On 03/25/2013 08:41 AM, Remi Collet wrote:
Le 25/03/2013 06:47, Laruence a écrit :
attached here:
https://bugs.php.net/patch-display.php?bug_id=64503patch=bison_build_2.patchrevision=latest
Tested under RHEL 6.4 (bison 2.4.1), Fedora 17 (bison 2.5) and Fedora 18
(bison 2.6.1). NTS and ZTS
On 03/25/2013 01:59 PM, Rasmus Lerdorf wrote:
On 03/25/2013 01:43 PM, Christopher Jones wrote:
Bison 2.3 with Oracle Linux 5.9 (and therefore with RHEL 5.9) gives this
error:
/home/cjones/php-5.5/Zend/zend_language_parser.y:50.1-5: invalid
directive: `%code'
/home/cjones/php-5.5/Zend
On 03/02/2013 09:42 AM, Christopher Jones wrote:
On 3/2/13 3:19 AM, Terry Ellison wrote:
On 02/03/13 09:34, Pierre Joye wrote:
Having it in peck right now allows that. But as of now it is not a PHP.net
project so it makes little sense to have it listed there.
On Mar 2, 2013 10:33 AM
On 3/2/13 3:19 AM, Terry Ellison wrote:
On 02/03/13 09:34, Pierre Joye wrote:
Having it in peck right now allows that. But as of now it is not a PHP.net
project so it makes little sense to have it listed there.
On Mar 2, 2013 10:33 AM, Terry Ellison te...@ellisons.org.uk
On 03/01/2013 04:15 PM, Matt Ficken wrote:
I am testing O+ on Windows with php 5.3, 5.4, and 5.5.
I have uploaded my O+ test results here:
http://windows.php.net/downloads/snaps/ostc/pftt/
Can you put your O+ php.ini settings up there as well?
Did you experiment with any options?
Putting
On 02/28/2013 05:54 AM, Ondřej Hošek wrote:
Hi,
yesterday, I submitted a patch to add a batch modification function to the
LDAP extension:
https://bugs.php.net/bug.php?id=64317
IMNSHO, this would be a very useful addition to PHP’s LDAP API (and I think
the submitter of bug 31209, among
On 02/27/2013 03:06 AM, Zeev Suraski wrote:
Are there any additional clarifications and/or unanswered questions people
are still waiting for, or can we move ahead to vote on the O+ inclusion RFC?
Zeev
Are there any updated guesstimates at how long integration into PHP 5.5 will
take?
On 02/27/2013 11:26 AM, Pierre Joye wrote:
On Wed, Feb 27, 2013 at 8:05 PM, Christopher Jones
christopher.jo...@oracle.com wrote:
Are there any updated guesstimates at how long integration into PHP 5.5 will
take?
There will be no integration, but the idea is to bundle
On 02/25/2013 08:14 AM, Nikita Popov wrote:
Hi internals!
PHP 5.4 added support for expressions of the kind (new Foo)-bar(), (new
Foo)-bar and (new Foo)['bar'].
I'd like to extend this support to any expression instead of just new.
Why should be do this? Because it's just an arbitrary
On 02/25/2013 04:33 PM, Sara Golemon wrote:
When it comes to changing syntax, there is no such thing as too small
of an RFC IMO. Runtime changes can occasionally be hand-waved, but
syntax changes are serious business.
Seeing this quoted makes me realize I expressed myself poorly. What I
On 02/21/2013 04:42 PM, Keyur Govande wrote:
Hi everyone,
With the 2 weeks discussion period up, I'm moving this RFC to the Voting
stage. I'd like to get this into 5.5.
Most of the reaction has been positive and is archived here:
http://marc.info/?t=13602158203r=1w=2
Please vote on
On 02/22/2013 10:22 AM, Christopher Jones wrote:
On 02/21/2013 04:42 PM, Keyur Govande wrote:
Hi everyone,
With the 2 weeks discussion period up, I'm moving this RFC to the Voting
stage. I'd like to get this into 5.5.
Most of the reaction has been positive and is archived here:
http
On 02/21/2013 03:02 AM, Florian Anderiasch wrote:
On 02/21/2013 08:14 AM, Pierre Joye wrote:
I do not have a single doubt. Why? Surveys are one of many ways to get
feedback. They have no contracting values but give us some numbers about
one rfc or another. That may help us to focus on one
On 02/20/2013 12:00 PM, Paul Reinheimer wrote:
Hi All,
My apologies for the intrusion, I'll keep this brief.
In many discussions over the past few months there has been talk about what
the community at large needs. Pierre said just earlier today:
I would also say it us time for us to get
On 02/19/2013 09:45 AM, Marcello Duarte wrote:
And just for you is also inaccurate. You will find that the
technologies I've been referring to are becoming the tools you will
use for DevOps, etc... tasks. Do you guys listen to people outside
of internals? It would be good to have a feedback
On 02/19/2013 03:08 PM, Terry Ellison wrote:
I guess that I should bite the bullet and switch to 5.5.
Yes.
I've been working on an evaluatorfork of APC optimized for CLI/GCI
which tackles a lot of these issues head on and performs reasonable
well, but I realise that this is a dead-end and
On 02/19/2013 11:22 PM, Klaus Ufo wrote:
Hi there !
We all know that the current PHP API has flaws. Maybe we could use namespaces
to build a new coherent PHP API ? Like :
- \arr
- \num
- \str
and so on. Advantages :
- no more global functions
- separation of concerns
- backward
On 02/16/2013 01:10 PM, Rasmus Lerdorf wrote:
On 02/16/2013 11:16 AM, Zeev Suraski wrote:
- Regarding name choice, here are some: ZopCache, Cachze, RunCachze.
Interesting names, I'm curious about pronunciation :)
I (mostly) pronounce cache the non-American way as kaysh. Cachze would be
On 02/18/2013 10:52 AM, Christopher Jones wrote:
I agree that unless we get Gopal-like inspiration (inclued, scream) for naming,
opcache is best.
In the so bad I can't resist sending it category is today's
semi-humorous name suggestion: Cajun. It sounds roughly like the
English
Hi Zeev,
I think people are keen to see Optimizer+ merged. Hopefully the RFC
can set expectations clear on what the short-term steps will be, and
what the bigger picture might look like. The middle-term tasks will
then work themselves out as we get to them (in true PHP fashion)
- What does
On 02/14/2013 08:02 AM, Nikita Popov wrote:
On Thu, Feb 14, 2013 at 4:21 PM, Zeev Suraski z...@zend.com
mailto:z...@zend.com wrote:
- Should the name reflect the code's main purpose (op-code caching),
and allowing a future use of optimizer for a more sophisticated
On 02/14/2013 07:21 AM, Zeev Suraski wrote:
Great to see.
The README covers much of the content (and in more detail) that I
previously
wanted to see in the RFC.
Excellent!
There are some things still missing from the RFC, though:
- do you see Optimizer+ being enabled (if not in PECL)
On 01/29/2013 06:10 AM, Ferenc Kovacs wrote:
On Fri, Sep 14, 2012 at 12:47 PM, Pierre Joye pierre@gmail.com wrote:
hi Ferenc,
Can you put that in the wiki too instead? So it can be clarified there
directly if necessary.
Thanks,
I've put it up under https://wiki.php.net/rfc/howto
On 01/30/2013 06:47 AM, Zeev Suraski wrote:
This is the kind of info the RFC (and then user doc) should have.
I updated the RFC with two extra sections - 'what's an opcode cache',
This section extremely general and doesn't explain what the expected
feature set might look like. I'm not
On 01/29/2013 12:30 AM, Zeev Suraski wrote:
By the way, I just realized the % gain wasn't all that self-explanatory -
it's vs. APC, not vs. plain PHP. I improved the doc to reflect both gains
vs. plain PHP and vs. APC.
Thanks for the feedback!
Zeev
Zeev,
It would be useful to link to
On 01/29/2013 04:27 PM, Rasmus Lerdorf wrote:
On 01/29/2013 04:17 PM, Christopher Jones wrote:
It would be useful to link to the current Optimizer+ doc from the RFC.
I believe the link is
http://static.zend.com/topics/Zend-Optimizer-User-Guide-v330-new.pdf
Different beast. Something like
On 01/24/2013 10:47 AM, Dennis Clarke wrote:
So here I am once again trying to build PHP 5.4.11 on a Solaris 10 server
with the following configure options :
So I think that I should be okay. Do I need to upgrade to curl
7.28.2 and then try building PHP 5.4.11 or am I sort of stuck here
at
On 01/23/2013 09:37 AM, Florian Anderiasch wrote:
On 01/21/2013 11:44 PM, Christopher Jones wrote:
Pierre,
Can you review this RFC and the votes? The wording 5.5 final
release needs assessing. You probably meant first 5.5 production
release. If anyone interpreted it as it is actually
On 01/22/2013 01:27 PM, Clint Priest wrote:
In terms of cost of maintenance, I was under the impression that
since I wrote it, I would be maintaining it which is why I applied
for and you approved a VCS account for me.
The concern is historical and not personal. Frequently the long-term
On 01/14/2013 01:18 AM, Pierre Joye wrote:
Arg, sorry :)
Here you go:
https://wiki.php.net/rfc/php53eol
Pierre,
Can you review this RFC and the votes? The wording 5.5 final
release needs assessing. You probably meant first 5.5 production
release. If anyone interpreted it as it is
[CC'ing internals.]
On 01/16/2013 03:15 PM, Paul Taulborg wrote:
On Wed, Jan 16, 2013 at 4:21 PM, Nuno Lopes nlop...@php.net wrote:
On Thu, Jan 10, 2013 at 4:59 PM, Nuno Lopes nlop...@php.net wrote:
On 01/07/2013 07:27 AM, Paul Taulborg wrote:
I would love to write this patch, I'm all in
On 01/15/2013 06:18 PM, Stas Malyshev wrote:
Hi!
I will try to wade through the logs tomorrow. At the moment I am doing
the same process on RHEL and seeing a bucket of failures also.
This URL has some potential to help, since it will show common failures
other people are seeing:
On 01/15/2013 12:09 PM, Dennis Clarke wrote:
Of course, if 2.6.5 is verified than it should be added to
bison_version_list in Zend/acinclude.m4. Feel free to regenerate the
parsers with it, review the test suite results, and create a github
pull request.
Anything outside of release
On 01/14/2013 01:55 PM, Gustavo Lopes wrote:
On Wed, 09 Jan 2013 23:45:03 +0100, Gustavo Lopes glo...@nebm.ist.utl.pt
wrote:
On Thu, 03 Jan 2013 11:40:31 +0100, Gustavo Lopes glo...@nebm.ist.utl.pt
wrote:
The algorithm behaves very poorly in this case because at each position of the
On 01/14/2013 05:16 PM, Dennis Clarke wrote:
Dear PHP/Zend folks :
This is a bug I think. I recently saw that PHP had been updated to 5.4.10
and I
decided to update my php bits in /usr/local. I was quite surprised to see in the
configure output this warning about bison :
checking for
On 12/28/2012 01:08 AM, Remi Collet wrote:
Le 24/12/2012 04:16, Igor Wiedler a écrit :
Hi Internals,
When test driving PHP-5.5 I ran into issues with a change of unpack behaviour. Archive_Tar which is
used by pecl and pear (`pecl install`) uses unpack with the a format character. On 5.4
it
On 01/09/2013 02:45 PM, Gustavo Lopes wrote:
On Thu, 03 Jan 2013 11:40:31 +0100, Gustavo Lopes glo...@nebm.ist.utl.pt
wrote:
The algorithm behaves very poorly in this case because at each position of the
text, all the substrings starting there and with size between m and n (where m
is the
On 12/21/2012 06:54 AM, Nikita Popov wrote:
If there are no further objections I'll commit this tomorrow.
Nikita
This feature needs documenting in Generator RFC before it is committed.
The RFC will be referenced by people new to the feature and so it
should have a complete list of changes.
On 12/20/2012 08:31 AM, Larry Garfield wrote:
On 12/19/12 10:30 PM, Christopher Jones wrote:
On 12/19/2012 03:18 PM, Larry Garfield wrote:
You could likely simplify the code even further using an infinite
iterator:
http://us1.php.net/infiniteiterator
$result = preg_replace_callback
On 12/20/2012 04:05 PM, David Muir wrote:
The curiosity (bug?) is the need to call rewind():
$replacements_iterator = new InfiniteIterator(new ArrayIterator($replacements));
$replacements_iterator-rewind(); // why is the rewind needed?
$result = preg_replace_callback(
'/word/',
On 12/19/2012 03:18 PM, Larry Garfield wrote:
You could likely simplify the code even further using an infinite iterator:
http://us1.php.net/infiniteiterator
$result = preg_replace_callback(
'/word/',
function($matches) use ($replacements_iterator) {
return
On 12/01/2012 10:21 AM, Paul Taulborg wrote:
[php_date.c patch]
Thanks for the patch. To ensure it isn't lost, can you open a bug at
https://bugs.php.net/ and attach it? And/or submit a pull request at
https://github.com/php/php-src
Regards,
Chris
--
christopher.jo...@oracle.com
On 11/13/2012 01:40 AM, Lester Caine wrote:
Christopher Jones wrote:
When users of 5.5 stumble on the new messages, we can then simply
point them to the RFC.
I think this is part of the problem. The material from the RFC's
should be used as a source to update the core documentation? Rather
On 11/12/2012 05:00 AM, Adam Harvey wrote:
Hi everyone,
I've written an RFC to cover deprecating ext/mysql in PHP 5.5:
https://wiki.php.net/rfc/mysql_deprecation. While we handled the soft
deprecation in the documentation purely via a straw poll on Internals,
I presume this will end up
On 11/12/2012 07:08 PM, Adam Harvey wrote:
On 13 November 2012 08:44, Christopher Jones
christopher.jo...@oracle.com wrote:
Adam, can you:
1. Add this link to the RFC?:
https://wikis.oracle.com/display/mysql/Converting+to+MySQLi
2. Mention how to turn off E_DEPRECATED warnings
On 08/08/2012 10:33 AM, Cristian Rodríguez wrote:
sapi/apache2filter/sapi_apache2.c | 11 +--
sapi/apache2handler/sapi_apache2.c | 12 ++--
2 files changed, 19 insertions(+), 4 deletions(-)
Patches to the mail list are very likely to get lost. It's probably
better to
On 07/31/2012 04:23 PM, Stan Vass wrote:
I'd like to point out some puzzling behaviors in Traits as they exist in the
production releases of PHP 5.4.
Regardless of the outcome of the mail thread, can you review the traits tests
and create new tests for
any behaviour not already covered?
On 07/30/2012 01:32 PM, Gustavo Lopes wrote:
3. There are other low-cost alternatives, namely the obvious one: pass the
object via an extra parameter instead of operating on $this directly and
unconditionally. This is really easy to do.
This kind of thing should be mentioned in the RFC.
On 07/26/2012 08:41 AM, Johannes Schlüter wrote:
I would therefore like to reduce the 5.3 pace.
This is reasonable.
The current idea would be to skip every second release (unless security
issues demand something else) both in release date as well as version
number.
Skipping numbers will
1 - 100 of 312 matches
Mail list logo