Generating phar.php
Generating phar.phar
PEAR package PHP_Archive not installed: generated phar will require PHP's
phar extension be enabled.
pharcommand.inc
directorytreeiterator.inc
clicommand.inc
directorygraphiterator.inc
invertedregexiterator.inc
.svn/prop-base/invertedregexiterator.inc.svn-ba
Johannes Schlüter wrote:
> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>
>> I'd like to consider instead using svn:externals to pull in PEAR stuff
>> directly from a STABLE branch from somewhere in the pear/ hierarchy.
>> This would allow us over at PEAR to push the installation phars
On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
> I'd like to consider instead using svn:externals to pull in PEAR stuff
> directly from a STABLE branch from somewhere in the pear/ hierarchy.
> This would allow us over at PEAR to push the installation phars into
> that branch at the same tim
On Fri, Jul 17, 2009 at 2:23 AM, Greg Beaver wrote:
>> Is it possible to have one single phar for all platforms? That would
>> already make the whole thing easier to manage.
>>
> This would be more challenging to do, but may be possible. The biggest
> problem is that go-pear is interactive, and i
Pierre Joye wrote:
> hi,
>
> On Fri, Jul 17, 2009 at 1:20 AM, Greg Beaver wrote:
>
>> Hi,
>>
>> I'd like to start a discussion on php-src/pear and how we can manage it
>> better for PHP 5.3, and to discuss the future of PEAR in PHP.
>>
>> First, take note that both internals@ and pear-dev@ are c
Pierre Joye wrote:
On Fri, Jul 17, 2009 at 12:45 AM, shire wrote:
Jani Taskinen wrote:
Rasmus Lerdorf wrote:
One of the benefits of svn is that we can do cross-branch commit pretty
easily now and thus avoid multiple similar commits with annoying MFH/MFB
commit log messages that are hard to tr
hi,
On Fri, Jul 17, 2009 at 1:20 AM, Greg Beaver wrote:
> Hi,
>
> I'd like to start a discussion on php-src/pear and how we can manage it
> better for PHP 5.3, and to discuss the future of PEAR in PHP.
>
> First, take note that both internals@ and pear-dev@ are copied on this
> email.
>
> For some
On 2009-07-16, Pierre Joye wrote:
> I doubt any tools can really help to automatically help to merge
> changes from one branch to another (in php). However there are many
> very good merging tools (with UI) out there to ease this process
> (meld, winmerge, etc.).
In that case it's more that if we
Hi,
I'd like to start a discussion on php-src/pear and how we can manage it
better for PHP 5.3, and to discuss the future of PEAR in PHP.
First, take note that both internals@ and pear-dev@ are copied on this
email.
For some background, currently the pear components are dynamically added
to a ch
On Fri, Jul 17, 2009 at 12:45 AM, shire wrote:
> Jani Taskinen wrote:
>>
>> Rasmus Lerdorf wrote:
>>>
>>> One of the benefits of svn is that we can do cross-branch commit pretty
>>> easily now and thus avoid multiple similar commits with annoying MFH/MFB
>>> commit log messages that are hard to tra
Greg Beaver wrote:
> Rasmus Lerdorf wrote:
>> One of the benefits of svn is that we can do cross-branch commit pretty
>> easily now and thus avoid multiple similar commits with annoying MFH/MFB
>> commit log messages that are hard to track.
>>
>> Please don't attempt to check out all of php/php-src
Rasmus Lerdorf wrote:
> One of the benefits of svn is that we can do cross-branch commit pretty
> easily now and thus avoid multiple similar commits with annoying MFH/MFB
> commit log messages that are hard to track.
>
> Please don't attempt to check out all of php/php-src or pecl. I made
> the m
Jeff Griffiths wrote:
On 16/07/09 3:45 PM, shire wrote:
...
Do we have a long-term plan of using actual merge commands/tools to
merge our branches rather than duplicating commits or manually merging?
I think this could speed up development and allow us to have more
control over releases, version
On 16/07/09 3:45 PM, shire wrote:
...
Do we have a long-term plan of using actual merge commands/tools to
merge our branches rather than duplicating commits or manually merging?
I think this could speed up development and allow us to have more
control over releases, versions, etc. I've seen cases
Jani Taskinen wrote:
Rasmus Lerdorf wrote:
One of the benefits of svn is that we can do cross-branch commit pretty
easily now and thus avoid multiple similar commits with annoying MFH/MFB
commit log messages that are hard to track.
I did a commit today on all 3 branches and it worked fine exce
On Jul 16, 2009, at 6:19 PM, Jani Taskinen wrote:
Or just to something more generic like php-commits@ ? The same with
zend-commits?
Only php-commits@ is necessary since there is no separate Zend stuff
anymore..?
Zend commits are still sent separately. From commit-email.php:
'|^php/ZendA
Rasmus Lerdorf wrote:
One of the benefits of svn is that we can do cross-branch commit pretty
easily now and thus avoid multiple similar commits with annoying MFH/MFB
commit log messages that are hard to track.
I did a commit today on all 3 branches and it worked fine except for the fact
that
Alright, I've implemented pretty much every single suggestion you
made :). Note that _php_array_to_envp() actually suffers the same
"modify in place" problem, but because it iterates the array twice (is
that REALLY so much better than allocating a few extra pointers or
calling perealloc() a
On 2009-07-14, David Soria Parra wrote:
> Hi List,
>
> in the last months I worked on adding DTrace probes to PHP and would
> like to start a discussion about the RFC and patch against trunk
> that can be found at:
>
> http://wiki.php.net/rfc/dtrace
If there are no other objects I will commit th
Uwe Schindler wrote:
Or just to something more generic like php-commits@ ? The same with
zend-commits?
Only php-commits@ is necessary since there is no separate Zend stuff anymore..?
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsu
One of the benefits of svn is that we can do cross-branch commit pretty
easily now and thus avoid multiple similar commits with annoying MFH/MFB
commit log messages that are hard to track.
Please don't attempt to check out all of php/php-src or pecl. I made
the mistake of checking out all of pecl
Or just to something more generic like php-commits@ ? The same with
zend-commits?
Uwe
-
Uwe Schindler
theta...@php.net - http://www.php.net
NSAPI SAPI developer
Bremen, Germany
> -Original Message-
> From: Andrey Hristov [mailto:p...@hristov.com]
> Sent: Thursday, July 16, 2009 7:36
On 2009-07-16, Andrey Hristov wrote:
> Hi,
> does it makes sense? Once we renamed php-dev to internals, so this won't
> be the first ML rename.
if we really need that we better use php-commits or something similar.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Hi,
does it makes sense? Once we renamed php-dev to internals, so this won't
be the first ML rename.
Best,
Andrey
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
It took me a day to get a binary gearman worker out of the PHP make system.
But it works (somehow).
Now I'd like to ask, whether it could be included in upstream PHP source? I'd
need a sponsor to guide me cleaning up everything.
Tomorrow I'll try to get source code caching with APC to work. It
On 07/14/2009 05:38 AM, Herman Radtke wrote:
This bug only exists in PHP 5.x. The unicode support in PHP 6 takes
care of it already, but I added a PHP 6 version of the test case as
well.
Committed. I fixed the test to work in all branches. :)
--Jani
--
PHP Internals - PHP Runtime Developme
Hi,
try:
___
class A
{
protected $a;
public function __construct()
{
if(!isset($this->a))
{
$this->a = 'd';
echo '1st';
}
unset($this->a);
if(!isset($this->a))
{
$this->a = 'g';
echo '2nd';
}
Patch files for php 5.x and 6 with a test.
--
Herman Radtke
hermanrad...@gmail.com | http://hermanradtke.com
Index: ext/standard/string.c
===
--- ext/standard/string.c (revision 284189)
+++ ext/standard/string.c (working
On Thu, Jul 16, 2009 at 5:54 AM, Philip Olson wrote:
> As for 'capturing related bugs', I imagine the [optional] tagging would help
> with that... or do you have something specific in mind?
Related bugs are more a list of bugs # related to a given one, or
being a dependency, a coma separated list
29 matches
Mail list logo
