On Tue, April 25, 2006 10:43 pm, Marco wrote:
> does
> anyone have any suggestions on how we can encourage the deployment of
> php
> 5?
Other routes:
Convince the webhosts it's 100% backwards-compatible, and easy to
upgrade, and provides better resource management so they can cram in
more users
Ah yes.
http://us3.php.net/manual/en/function.openssl-pkey-export.php almost
does what you want... but only works on private keys.
I'd welcome a patch for that too.
--Wez.
On 4/25/06, Brandon Fosdick <[EMAIL PROTECTED]> wrote:
> Wez Furlong wrote:
> > Like this:
> > http://us2.php.net/manual/en/
On 25-Apr-06, at 12:35 PM, Steph Fox wrote:
Hi Wez,
The problem with moving ext/skeleton is that we'll end up shipping
PHP
without an extension template of any kind. Almost every single PHP
book that talks about writing extensions uses ext_skel to do so.
Since when have existing books be
Right. Throwing exceptions from output handler or INI reader may not
be optimal.
What did you think about the user defined error handler though?
-Andrei
On Apr 24, 2006, at 10:16 PM, Andi Gutmans wrote:
I'm wondering whether it's technically feasible that any places
where such a conversio
I can't see any negative points to keeping ext/skeleton in the tree.
I can't see any positive ones :)
It provides a basic template for making new extensions without having to
go searching through PECL, this is a big + IMHO.
OK, fair enough. Is anyone going to answer the rather more impor
On 4/25/06, Steph Fox <[EMAIL PROTECTED]> wrote:
> Since when have existing books been a reason not to change something?
Given the lack of documentation on this topic and the fact that
ext_skel and ext/skeleton are pretty much just plain text, I think
it's a pretty damned good reason.
> > I can't
Hello Jochem,
Tuesday, April 25, 2006, 3:15:52 PM, you wrote:
> Petar Nedyalkov wrote:
>> On Tuesday 25 April 2006 14:30, Edin Kadribasic wrote:
>>
>>>Hi,
>>>
>>>I was wondering if someone could enlighten me why it is not possible to
>>>create on-the-fly static properties:
>>>
>>>php -r 'class f
On Tue, 25 Apr 2006, Wez Furlong wrote:
> The problem with moving ext/skeleton is that we'll end up shipping PHP
> without an extension template of any kind. Almost every single PHP
> book that talks about writing extensions uses ext_skel to do so.
>
> Giving PECL_gen some good press is a differ
I've remembered of one more idea: gcov.php.net
That site has an enormous potential to help us building a bug-free PHP. But
this site needs some work on usability. It could for example e-mail the
developers list when there was a regression on a test or when it found a new
memory leak.
For exampl
Nuno Lopes wrote:
I've remembered of one more idea: gcov.php.net
That site has an enormous potential to help us building a bug-free PHP.
But this site needs some work on usability. It could for example e-mail
the developers list when there was a regression on a test or when it
found a new memo
Marcus Boerger wrote:
It is just some decision that was taken that the newer OO stuff should be a
bit more strict.
I don't remember any such decision. I don't even remember a discussion
about it. I'm aware of the efforts of some people to make PHP less PHP
and more Java and thus we end up in
Marcus Boerger wrote:
Hello Jochem,
hi Marcus,
thanks for your response (It remains a bit of a honour when
someone from the dev ranks takes time to give feedback -
new insight often follows as secondary benefit).
Tuesday, April 25, 2006, 3:15:52 PM, you wrote:
Petar Nedyalkov wrote:
On
Nuno Lopes wrote:
I've remembered of one more idea: gcov.php.net
That site has an enormous potential to help us building a bug-free PHP.
But this site needs some work on usability. It could for example e-mail
the developers list when there was a regression on a test or when it
found a new memo
In PHP4, you could do:
function test()
{
return array(1,2,3);
}
$var = array_shift(test());
PHP 5.0 broke this. There was a fatal error on the array_shift that
only variables could be passed by reference. There was a good argument
for it. So, we started migrating our code.
Well, s
Brian Moon wrote:
In PHP4, you could do:
function test()
{
return array(1,2,3);
}
$var = array_shift(test());
PHP 5.0 broke this. There was a fatal error on the array_shift that
only variables could be passed by reference. There was a good argument
for it. So, we started migrating
Hello Rasmus,
RL> In 5.1 this now throws an E_STRICT instead of a warning. It is still a
RL> bad idea to pass a tempvar by reference, so yes, you should strive to
RL> write E_STRICT clean code.
At the possible expense of being blamed and flamed, I'll say it...
ifsetor($var, 'default') would go
Wez Furlong wrote:
Ah yes.
http://us3.php.net/manual/en/function.openssl-pkey-export.php almost
does what you want... but only works on private keys.
I'd welcome a patch for that too.
Do you want separate patches for PKCS12 and PEM keys or should it be all one
patch?
Has anything changed tha
In 5.1 this now throws an E_STRICT instead of a warning. It is still a
bad idea to pass a tempvar by reference, so yes, you should strive to
write E_STRICT clean code.
Yeah, its more of a question of rewriting 6 years of PHP or not. We
were half way done when we upgraded the dev machines to
I want to know more detail in php extension and I want to create php extension
for my website
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
19 matches
Mail list logo
