On Fri, Feb 22, 2013 at 10:39 AM, Johannes Schlüter
wrote:
> On Fri, 2013-02-22 at 08:44 +0100, Martin Keckeis wrote:
>
> > I think there may come many critics maybe, but why not move those things
> > also to github?
> > It's used by many people. it works, it's easy!
>
> It is easily two steps bac
On Fri, Feb 22, 2013 at 8:44 AM, Martin Keckeis
wrote:
> 2013/2/21 Johannes Schlüter
>
> > On Thu, 2013-02-21 at 19:13 +0100, Pascal Chevrel wrote:
> > >
> > > I am specifically thinking of Bugzilla which is already used by many
> > > open source projects. It has a lot more features than your cur
On Fri, 2013-02-22 at 08:44 +0100, Martin Keckeis wrote:
> I think there may come many critics maybe, but why not move those things
> also to github?
> It's used by many people. it works, it's easy!
It is easily two steps back. Yay! (Tags are funny but don't help with
categorization of bugs on PH
2013/2/21 Johannes Schlüter
> On Thu, 2013-02-21 at 19:13 +0100, Pascal Chevrel wrote:
> >
> > I am specifically thinking of Bugzilla which is already used by many
> > open source projects. It has a lot more features than your current
> > bug
> > tracking system, it scales for large projects and
Hi!
> F.e., how long have we been battled for annotations? With all
> respects, it is about being blind and stubborn to say that PHP should
> not have annotations. But due to some "I'm happy with what we have
It is about being blind and stubborn to hold opinion different than
yours. And *this* no
Hello List,
how about sort of Tick-Tock development model?
Tick = optimize/bugfix
Tock = shiny new features
e.g. http://en.wikipedia.org/wiki/Intel_Tick-Tock
cryptocompress
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 02/21/2013 01:04 PM, Johannes Schlüter wrote:
> On Thu, 2013-02-21 at 17:06 +0100, Marco Pivetta wrote:
>> On 21 February 2013 17:04, Johannes Schlüter wrote:
>>
>>> The quoted business decision was "We want something stable and fast", an
>>> emphasis of fixing bugs over adding new ones. This s
On Thu, 2013-02-21 at 17:06 +0100, Marco Pivetta wrote:
> On 21 February 2013 17:04, Johannes Schlüter wrote:
>
> > The quoted business decision was "We want something stable and fast", an
> > emphasis of fixing bugs over adding new ones. This sounds sane to me.
> Doesn't exclude new features th
Arvids Godjuks wrote:
In principle, as a user-land developer, I agree with the motion. It's too
much fancy new shiny stuff lately and no actual improvement on the old
stuff that really needs fixing or updating/rewriting (PDO anyone? Years
behind every db driver extension there is in PHP, and as f
On Thu, 2013-02-21 at 19:13 +0100, Pascal Chevrel wrote:
>
> I am specifically thinking of Bugzilla which is already used by many
> open source projects. It has a lot more features than your current
> bug
> tracking system, it scales for large projects and it has a few
> Mozilla
> employees wor
On Thu, Feb 21, 2013 at 10:13 AM, Pascal Chevrel wrote:
> I am specifically thinking of Bugzilla which is already used by many open
> source projects. It has a lot more features than your current bug tracking
> system, it scales for large projects and it has a few Mozilla employees
> working full
Le 21/02/2013 18:56, Ferenc Kovacs a écrit :
it is, and it is a chicken and egg problem:
even though that the usual "my C-fu is weak" argument doesn't apply there,
we still lack contributors, and the archaic nature of the current codebase
doesn't really helps bringing in new people.
even if a ne
replying inline
I think it would be helpful to have something like a roadmap with various
> features and changes both in regards to language and features as well
> as performance.
>
We have discussed before and the problem is the nature of the project: it
is an open source project where the cont
On 2013-02-21, Rasmus Lerdorf wrote:
> Personally I would love to see more RFCs focusing on performance and
> less on syntax changes. Of course, a syntax change RFC, and even the
> initial (often shaky) implementation of a syntax-related change is much
> much easier to whip up than the deep analys
On 21.02.2013, at 20:08, Levi Morrison wrote:
>> Personally I would love to see more RFCs focusing on performance and
>> less on syntax changes.
>
> Some recent tests I performed indicate that JavaScript and Dart are
> both significantly faster than PHP when working with just arrays and
> numbe
Hello,
On Thu, Feb 21, 2013 at 5:30 PM, Rasmus Lerdorf wrote:
> In the slice of the "community" where I spend most of my time,
> medium-to-large companies using PHP with their own custom code on
> hundreds to thousands or even 10's of thousands of servers, neither
> annotations nor getter/setter
> Personally I would love to see more RFCs focusing on performance and
> less on syntax changes.
Some recent tests I performed indicate that JavaScript and Dart are
both significantly faster than PHP when working with just arrays and
numbers. If anyone is interested I can provide the test code for
On 21 February 2013 17:04, Johannes Schlüter wrote:
> The quoted business decision was "We want something stable and fast", an
> emphasis of fixing bugs over adding new ones. This sounds sane to me.
>
> johannes
>
>
>
Doesn't exclude new features then: so what is this all about?
Marco Pivetta
h
On Thu, 2013-02-21 at 16:54 +0100, Marco Pivetta wrote:
> No hard feelings, but it would be awesome if that part of the "community"
> (the one that basically avoids social coding as far as I can see, not to be
> taken as a sin, but still "meh") didn't just try to hold back PHP because
> of business
On 21 February 2013 16:30, Rasmus Lerdorf wrote:
> In the slice of the "community" where I spend most of my time
>
No hard feelings, but it would be awesome if that part of the "community"
(the one that basically avoids social coding as far as I can see, not to be
taken as a sin, but still "meh"
Hello, didn't read the whole thread, just a few messages at the start. But
because I'm replying to the starting message, it's not relevant :)
In principle, as a user-land developer, I agree with the motion. It's too
much fancy new shiny stuff lately and no actual improvement on the old
stuff that
In the slice of the "community" where I spend most of my time,
medium-to-large companies using PHP with their own custom code on
hundreds to thousands or even 10's of thousands of servers, neither
annotations nor getter/setter are anywhere on their wishlist radar. What
they most desire is performan
On Feb 21, 2013, at 1:56 AM, Zeev Suraski wrote:
> There used to be a language that was the Queen of the Web. It was full of
> clever syntax. It prided itself on having a variety of expressive ways of
> doing the same thing. You're on the mailing list of the language that
> dethroned it.
Thi
> -Original Message-
> From: Pierre Joye [mailto:pierre@gmail.com]
> Sent: Thursday, February 21, 2013 4:08 PM
> To: Zeev Suraski
> Cc: Florin Razvan Patan; Lars Strojny; Derick Rethans; PHP Developers
Mailing
> List
> Subject: Re: [PHP-DEV] Give the Language a Res
hi,
On Thu, Feb 21, 2013 at 2:59 PM, Zeev Suraski wrote:
> That's not adaptation in my book. That's addition. It's not the technology
> landscape that changed that now you need annotations; It's that some people
> consider this feature cool and useful, and want to import it into PHP
> althoug
> -Original Message-
> From: Florin Razvan Patan [mailto:florinpa...@gmail.com]
> Sent: Thursday, February 21, 2013 3:15 PM
> To: Zeev Suraski
> Cc: Lars Strojny; Derick Rethans; PHP Developers Mailing List
> Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd)
> > People who think differently from you are not necessarily blind of
> > stubborn. I honestly think that those comments were completely out of
> > line in several different ways.
>
> It is not my opinion but a simple fact.
That comment would have been funny if it wasn't sad. I'll leave it at
t
Hello,
This might sound as a rant but I assure you it's not.
It's just how I see the things from my perspective and that of
my colleagues/employer.
On Thu, Feb 21, 2013 at 11:56 AM, Zeev Suraski wrote:
> What you're bringing up is not at all about adapting. Adapting is
> something we do at the
Pierre Joye wrote:
>Regarding 'voting with feet', it's an idiom, look it up.
I know, still do not think it fits as comment either here.
I read this as simply "People are not leaving PHP in droves simply because it
does not have xxx" - actually the opposite, but that growth in use is not into
Zeev,
On Thu, Feb 21, 2013 at 12:24 PM, Zeev Suraski wrote:
> Pierre,
>
> People who think differently from you are not necessarily blind of
> stubborn. I honestly think that those comments were completely out of
> line in several different ways.
It is not my opinion but a simple fact. Yes, you
On Wed, Feb 20, 2013 at 7:18 PM, Derick Rethans wrote:
> Once you're done thinking, decide for yourself. Does it make sense to be
> discussing new language level features every other week? Or should we,
> perhaps,
> invest more in other fronts, which would be beneficial for a far bigger
> audie
Here is a counterpoint to that expressed by Lars. Many if not most
shared hosting providers don't offer PHP 5.4 yet. Ditto many
enterprises have yet to adopt it. The main reason? I think its that
old Backwards Compatibility issue that has been discussed heavily on
this DL.
When major apps
gt; From: Pierre Joye [mailto:pierre@gmail.com]
> Sent: Thursday, February 21, 2013 12:09 PM
> To: Zeev Suraski
> Cc: Lars Strojny; Derick Rethans; PHP Developers Mailing List
> Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd)
>
> hi Zeev,
>
> On Thu, Feb 21, 20
Zeev Suraski wrote:
There used to be a language that was the Queen of the Web. It was full of
clever syntax. It prided itself on having a variety of expressive ways of
doing the same thing. You're on the mailing list of the language that
dethroned it.
And the majority of END USERS are more tha
hi Zeev,
On Thu, Feb 21, 2013 at 10:56 AM, Zeev Suraski wrote:
> What you're bringing up is not at all about adapting. Adapting is
> something we do at the extensions, frameworks and tools levels. I'm happy
> to say PHP's ecosystem here is very healthy, in my opinion.
Yes, most of the time. Bu
mailing list of the language that
dethroned it.
Zeev
> -Original Message-
> From: Lars Strojny [mailto:l...@strojny.net]
> Sent: Thursday, February 21, 2013 1:15 AM
> To: Derick Rethans; PHP Developers Mailing List
> Subject: Re: [PHP-DEV] Give the Language a Rest mot
hi,
On Thu, Feb 21, 2013 at 10:45 AM, Eloy Bote Falcon wrote:
> Agree. There are only a few core devs working daily in the PHP
> internals. I would say please give the Language (and devs) a rest
> motion, because there are a lot of bugs and work to be done but I'm
> afraid that is more easy/funn
2013/2/20 Derick Rethans :
> Looks like it is time to forward this email from 2006 again:
>
> -- Forwarded message --
> Date: Thu, 09 Mar 2006 12:57:32 +0200
> From: Zeev Suraski
> To: internals@lists.php.net
> Subject: [PHP-DEV] Give the Language a Rest m
Levi Morrison wrote:
>> - 5.3: goto. A good thing we can do it. I'm not sure for what exactly but I
>> am sure there is somebody out there :)
>
> An associate of mine used it in his HTTP message parser. He's sure
> glad it's there :)
>
Conversely, I have two HTTP message parsers that I maintai
> - 5.3: goto. A good thing we can do it. I'm not sure for what exactly but I
> am sure there is somebody out there :)
An associate of mine used it in his HTTP message parser. He's sure
glad it's there :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www
.
cu,
Lars
Am 20.02.2013 um 19:18 schrieb Derick Rethans :
> Looks like it is time to forward this email from 2006 again:
>
> -- Forwarded message --
> Date: Thu, 09 Mar 2006 12:57:32 +0200
> From: Zeev Suraski
> To: internals@lists.php.net
> Subject: [PHP-DEV] Give
- Forwarded message --
> Date: Thu, 09 Mar 2006 12:57:32 +0200
> From: Zeev Suraski
> To: internals@lists.php.net
> Subject: [PHP-DEV] Give the Language a Rest motion
>
> I'd like to raise a motion to 'Give the Language a Rest'.
>
> Almost a decade since we start
Looks like it is time to forward this email from 2006 again:
-- Forwarded message --
Date: Thu, 09 Mar 2006 12:57:32 +0200
From: Zeev Suraski
To: internals@lists.php.net
Subject: [PHP-DEV] Give the Language a Rest motion
I'd like to raise a motion to 'Give the Langu
On Wed, Jun 29, 2011 at 4:57 PM, Hannes Magnusson
wrote:
> No.
> Some people just wanted some bugsweb so an old database was restored
> rather then waiting few hours for the actual data export.
The "some people" actually make it so that bugs.php.net was available
by the time 5.4.0 was released.
On Wed, Jun 29, 2011 at 4:36 PM, Pascal COURTOIS
wrote:
> bug 54460 has disapeared from bugs.php.net . Is due to the crash ?
Yes, the data was not available by the time we release PHP
5.4.0-alpha1. So we went with an alternative and temporary solution,
see http://news.php.net/php.internals/5363
On Jun 29, 2011, at 7:43 AM, Paul Dragoonis wrote:
> On Wed, Jun 29, 2011 at 3:36 PM, Pascal COURTOIS
> wrote:
>> Le 16/06/2011 08:10, Stas Malyshev a écrit :
>>> Hi!
>>>
what I did every single time. Among all my bug reports I had one
answer from decoder-...@own-hero.net (thanks to h
Le 29/06/2011 16:57, Hannes Magnusson a écrit :
> We have the data now and work is now ongoing migrating the two now.
> museum is also up, and snaps will probably be running before the weekend.
great, thanks :-)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
On Wed, Jun 29, 2011 at 16:43, Paul Dragoonis wrote:
> On Wed, Jun 29, 2011 at 3:36 PM, Pascal COURTOIS
> wrote:
>> Le 16/06/2011 08:10, Stas Malyshev a écrit :
>>> Hi!
>>>
what I did every single time. Among all my bug reports I had one
answer from decoder-...@own-hero.net (thanks to h
On Wed, Jun 29, 2011 at 3:36 PM, Pascal COURTOIS
wrote:
> Le 16/06/2011 08:10, Stas Malyshev a écrit :
>> Hi!
>>
>>> what I did every single time. Among all my bug reports I had one
>>> answer from decoder-...@own-hero.net (thanks to him) who reduced
>>> the test case for a memory leak (bug 54460)
Le 16/06/2011 08:10, Stas Malyshev a écrit :
> Hi!
>
>> what I did every single time. Among all my bug reports I had one
>> answer from decoder-...@own-hero.net (thanks to him) who reduced
>> the test case for a memory leak (bug 54460). I'm not talking about
>> bugs in modules but bugs in *core* w
On 06/16/2011 05:32 PM, Stas Malyshev wrote:
> Hi!
>
>> I'm not saying there aren't any. There are known leaks in compile_file()
>> when you throw an exception like that, so if you call a huge amount of
>> these within a single request, you are going to have problems. But that
>
> You actually ca
Le 16/06/2011 18:11, Andi Gutmans a écrit :
> I have some news for you. Ruby has crashes, Python has crashes,
Probably. any references about that ?
> even Java has security issues and crashes (check out the Java bug database.
> It's bigger than ours).
IMHO java is a big s**t but that's rea
Hi!
I'm not saying there aren't any. There are known leaks in compile_file()
when you throw an exception like that, so if you call a huge amount of
these within a single request, you are going to have problems. But that
You actually can't call huge amount of these in one request, as this
part
>-Original Message-
>From: Pascal COURTOIS [mailto:pascal.court...@nouvo.com]
>Sent: Thursday, June 16, 2011 12:28 AM
>To: Lester Caine
>Cc: PHP internals
>Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd)
>
>Le 16/06/2011 09:19, Lester Caine a écrit :
Le 16/06/2011 13:42, Rasmus a écrit :
> On 06/16/2011 11:40 AM, Pascal COURTOIS wrote:
>> Le 16/06/2011 12:31, Rasmus a écrit :
>>> On 06/16/2011 11:03 AM, Pascal COURTOIS wrote:
If you followed the thread you have seen the reduced test case is
VERY short and the ONLY constructions invol
On 06/16/2011 12:42 PM, Rasmus wrote:
> On 06/16/2011 11:40 AM, Pascal COURTOIS wrote:
>> Le 16/06/2011 12:31, Rasmus a écrit :
>>> On 06/16/2011 11:03 AM, Pascal COURTOIS wrote:
If you followed the thread you have seen the reduced test case is
VERY short and the ONLY constructions invol
On 06/16/2011 11:40 AM, Pascal COURTOIS wrote:
> Le 16/06/2011 12:31, Rasmus a écrit :
>> On 06/16/2011 11:03 AM, Pascal COURTOIS wrote:
>>> If you followed the thread you have seen the reduced test case is
>>> VERY short and the ONLY constructions involved are user functions and
>>> exceptions. F
On Thu, 2011-06-16 at 12:26 +0200, Pascal COURTOIS wrote:
> Le 16/06/2011 12:12, Pierre Joye a écrit :
>
> > It is not what Johannes said and we do fix bugs every single day. What
> > Johannes said is that we can't force a volunteer to do something
> > specific instead of what he wants to do.
> >
Le 16/06/2011 12:31, Rasmus a écrit :
> On 06/16/2011 11:03 AM, Pascal COURTOIS wrote:
>> If you followed the thread you have seen the reduced test case is
>> VERY short and the ONLY constructions involved are user functions and
>> exceptions. FULL STOP. Not even a single addition nor a loop nor n
On 06/16/2011 11:03 AM, Pascal COURTOIS wrote:
> If you followed the thread you have seen the reduced test case is
> VERY short and the ONLY constructions involved are user functions and
> exceptions. FULL STOP. Not even a single addition nor a loop nor nothing.
> I can't imagine nobody uses user
Le 16/06/2011 12:12, Pierre Joye a écrit :
> It is not what Johannes said and we do fix bugs every single day. What
> Johannes said is that we can't force a volunteer to do something
> specific instead of what he wants to do.
>
> It is also totally off topic btw.
It is really on topic since le
2011/6/16 Pascal COURTOIS :
> I know. I also have a GPL project. Nonetheless some societies use it,
> and some people rely on it to get paid. I have absolutely no legal contract
> with anyone but I have a moral contract and when I'm signaled a bug, it is
> mostly
> fixed within few hours. I just
Le 16/06/2011 11:36, Johannes Schlüter a écrit :
> On Thu, 2011-06-16 at 08:12 +0200, Pascal COURTOIS wrote:
>> Le 16/06/2011 08:01, dukeofgaming a écrit :
>>
>>> Sorry if the question is dumb, but, how many core developers does PHP have?,
>>> how many in total (including non-core contributors)?.
On Thu, 2011-06-16 at 08:12 +0200, Pascal COURTOIS wrote:
> Le 16/06/2011 08:01, dukeofgaming a écrit :
>
> > Sorry if the question is dumb, but, how many core developers does PHP have?,
> > how many in total (including non-core contributors)?.
>
> That's not the point. Whatever the project is,
On Thu, Jun 16, 2011 at 3:46 AM, Andi Gutmans wrote:
>>-Original Message-
>>From: Pierre Joye [mailto:pierre@gmail.com]
>>Sent: Wednesday, June 15, 2011 2:33 AM
>>To: Andi Gutmans
>>Cc: Derick Rethans; PHP Developers Mailing List
>>Subject: Re
Le 16/06/2011 10:12, Stas Malyshev a écrit :
> Hi!
>
> On 6/16/11 1:05 AM, Pascal COURTOIS wrote:
>> If you call "minuscule" a leak that requires more than 128Mb as it
>> normally requires about 4Mb, then it's minuscule but whatever you
>> name it it just does not run.
>
> Sorry, if your example
Hi!
On 6/16/11 1:05 AM, Pascal COURTOIS wrote:
If you call "minuscule" a leak that requires more than 128Mb as it
normally requires about 4Mb, then it's minuscule but whatever you name
it it just does not run.
Sorry, if your example generates memory footprint of 128Mb, something is
serious
Le 16/06/2011 09:56, Stas Malyshev a écrit :
> On 6/15/11 11:38 PM, Pascal COURTOIS wrote:
>> as I said earlier, test case was reduced to:
>
> The leaks you'll be seeing in this code is probably caused by the
> fact that main function (i.e. global context) is not destroyed when
> exit() is called,
On 6/15/11 11:38 PM, Pascal COURTOIS wrote:
as I said earlier, test case was reduced to:
The leaks you'll be seeing in this code is probably caused by the fact
that main function (i.e. global context) is not destroyed when exit() is
called, since . It can be argued as a bug, but very minor
Le 16/06/2011 09:29, Stas Malyshev a écrit :
> On 6/15/11 11:38 PM, Pascal COURTOIS wrote:
>>In bug 614904 I submitted a TWO lines program which crashed PHP on
>> a absolutely standard i386 debian install. I got no answer.
>> Of course the bug disapeared in following versions of PHP but what is
On 6/15/11 11:38 PM, Pascal COURTOIS wrote:
In bug 614904 I submitted a TWO lines program which crashed PHP on
a absolutely standard i386 debian install. I got no answer.
Of course the bug disapeared in following versions of PHP but what is fixed ?
Not as far as I know.
614904 doesn't look l
Le 16/06/2011 09:19, Lester Caine a écrit :
>>when you have a bug in PHP it should not ever ever crash PHP and
>> unfortunately I encountered that case dozens of times.
> At least on Linux is just recovers and carries on
If PHP crashes, yes, it recovers but it's VERY resource and time consum
On Jun 15, 2011, at 11:34 PM, dukeofgaming wrote:
> On Thu, Jun 16, 2011 at 1:12 AM, Pascal COURTOIS
> wrote:
>
>> Le 16/06/2011 08:01, dukeofgaming a écrit :
>>
>>> Sorry if the question is dumb, but, how many core developers does PHP
>> have?,
>>> how many in total (including non-core contrib
Pascal COURTOIS wrote:
Like Stas I have
never had problems with the stability of PHP5 in 10 years of running
it.
PHP5 did not exist 10 years ago ;-)
OK coming on 8 years ... seems longer :)
I looked at PHP4, but PHP5 was at release candidate stage so I decided that I'd
skip straight to tha
Le 16/06/2011 08:52, Lester Caine a écrit :
> Pascal I am sure that many people here would be more than happy to
> hear about particular problems you are hitting.
Ok, then why when I signal a bug noone cares ?
> Like Stas I have
> never had problems with the stability of PHP5 in 10 years of r
Pascal COURTOIS wrote:
What I need is a very stable language on which I can rely and I'm
>> very sad to to say PHP is getting worse and worse on that point of
>> view versions after versions.
>
> I can not contradict your experience, it is what it is, but my
> experience for years working wi
Le 16/06/2011 08:10, Stas Malyshev a écrit :
> Hi!
>
>> what I did every single time. Among all my bug reports I had one
>> answer from decoder-...@own-hero.net (thanks to him) who reduced
>> the test case for a memory leak (bug 54460). I'm not talking about
>> bugs in modules but bugs in *core* w
On Thu, Jun 16, 2011 at 1:12 AM, Pascal COURTOIS
wrote:
> Le 16/06/2011 08:01, dukeofgaming a écrit :
>
> > Sorry if the question is dumb, but, how many core developers does PHP
> have?,
> > how many in total (including non-core contributors)?.
>
> That's not the point. Whatever the project is, e
On Wed, 15 Jun 2011 23:10:24 -0700, Stas Malyshev wrote:
> Hi!
>
>>what I did every single time. Among all my bug reports I had one
>>answer
Stas, how I can i finally persuade you to quote the name of the people
you're replying to? :) I find it very hard to follow any discussion
you'r
Le 16/06/2011 08:01, dukeofgaming a écrit :
> Sorry if the question is dumb, but, how many core developers does PHP have?,
> how many in total (including non-core contributors)?.
That's not the point. Whatever the project is, every developer should fix
existing bugs before even thinking about
Hi!
what I did every single time. Among all my bug reports I had one answer
from decoder-...@own-hero.net (thanks to him) who reduced the test case
for a memory leak (bug 54460). I'm not talking about bugs in modules
but bugs in *core* which can be reproduced with few lines of *core* PHP.
I
On Thu, Jun 16, 2011 at 12:14 AM, Pascal COURTOIS wrote:
> Le 16/06/2011 04:36, dukeofgaming a écrit :
> > Hi,
> >
> > I think that —in any context— the "if it aint broke don't fix it" is a
> very
> > depressing attitude to have, and a very wrong one in any open source
> > community.
>
> What I
Le 16/06/2011 07:23, Stas Malyshev a écrit :
> Hi!
>
>> On every PHP project I work on I had to find workarounds because
>> PHP crashes. Behaviour bugs (feature not working as intended) are
>> annoying but memory leaks and memory corruptions are just a no no
>> no in production environment. The on
Hi!
On every PHP project I work on I had to find workarounds because PHP crashes.
Behaviour bugs (feature not working as intended) are annoying but memory leaks
and
memory corruptions are just a no no no in production environment. The only way
A key to fixing memory corruption is providing
Le 16/06/2011 04:36, dukeofgaming a écrit :
> Hi,
>
> I think that —in any context— the "if it aint broke don't fix it" is a very
> depressing attitude to have, and a very wrong one in any open source
> community.
What I feel depressing is the urge of the PHP core team to fix working
features
ailto:dukeofgam...@gmail.com]
Sent: Wednesday, June 15, 2011 7:36 PM
To: Andi Gutmans
Cc: Pierre Joye; Derick Rethans; PHP Developers Mailing List
Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd)
Hi,
I think that -in any context- the "if it aint broke don't fix it" is
1 at 8:46 PM, Andi Gutmans wrote:
> >-Original Message-
> >From: Pierre Joye [mailto:pierre@gmail.com]
> >Sent: Wednesday, June 15, 2011 2:33 AM
> >To: Andi Gutmans
> >Cc: Derick Rethans; PHP Developers Mailing List
> >Subject: Re: [PHP-DEV] G
>-Original Message-
>From: Pierre Joye [mailto:pierre@gmail.com]
>Sent: Wednesday, June 15, 2011 2:33 AM
>To: Andi Gutmans
>Cc: Derick Rethans; PHP Developers Mailing List
>Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd)
>
>On Wed, Jun 15, 2011
On 2011-06-15, Stas Malyshev wrote:
> Hi!
>
>> Stas, on a different note, weren't we going to roll a 5.4 alpha?
>
> I was going to write about it soon, but since you asked: I was waiting
> for RFC/voting discussion and vote in hope that we could get it all
> ready before the alpha, but it looks
Hi!
The original plan was this week, so maybe this Thursday?
After some consideration, we decided to do it on next Monday, the 20th.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Development Mailing List
To u
On Wed, Jun 15, 2011 at 7:02 AM, Andi Gutmans wrote:
> Hence my suggestion to bundle MongoDB extension and possibly work on
> additional extensions. Some of my suggestions probably rightfully didn't get
> much interest such as Thrift.
See my comment in your other thread and below.
> Maybe we
+1, for Thursday :-)
-邮件原件-
发件人: Stas Malyshev [mailto:smalys...@sugarcrm.com]
发送时间: 2011年6月15日 15:24
收件人: Andi Gutmans
抄送: PHP Developers Mailing List
主题: [PHP-DEV] Re: 5.4 alpha, was: [PHP-DEV] Give the Language a Rest
motion (fwd)
Hi!
> Stas, on a different note, weren't we
Hi!
Stas, on a different note, weren't we going to roll a 5.4 alpha?
I was going to write about it soon, but since you asked: I was waiting
for RFC/voting discussion and vote in hope that we could get it all
ready before the alpha, but it looks like it is taking longer than
expected. So I t
PHP Developers Mailing List
>Subject: [PHP-DEV] Give the Language a Rest motion (fwd)
>
>Hi,
>
>Short-array syntax, Native JSON, "Currying". I can almost only say one thing:
>WHY?!
>
>And because of that, I'd like to forward a mail by Zeev from a few years ago. I
On Tue, Jun 7, 2011 at 1:04 PM, Derick Rethans wrote:
> Hi,
>
> Short-array syntax, Native JSON, "Currying". I can
> almost only say one thing: WHY?!
>
> And because of that, I'd like to forward a mail by Zeev from a few years
> ago. I think it applies now even more than then:
>
> snip
I think t
On Tue, Jun 7, 2011 at 1:04 PM, Derick Rethans wrote:
> Hi,
>
> Short-array syntax, Native JSON, "Currying". I can
> almost only say one thing: WHY?!
>
> And because of that, I'd like to forward a mail by Zeev from a few years
> ago. I think it applies now even more than then:
I'd to disagree.
I
7:32 +0200
From: Zeev Suraski
To: internals@lists.php.net
Subject: [PHP-DEV] Give the Language a Rest motion
I'd like to raise a motion to 'Give the Language a Rest'.
Almost a decade since we started with the 2nd iteration on the syntax (PHP 3),
and 2 more major versions since
FWIW, I support this motion.
I am never a fan of the software lifecycle that looks like
"here's a useful technology, now we just need this,
and this...etc. ad nausea". Why?
(1) Adds complexity
(2) You often get pulled out of your original design philosophy
which puts the code's architectu
emon; internals@lists.php.net
> Subject: Re: [PHP-DEV] Give the Language a Rest motion
>
>
> No speed boost with opcode caches, which will be bundled in PHP 6 :)
>
> Zeev
>
> At 01:15 10/03/2006, Marcus Boerger wrote:
> >Hello Sara,
> >
> > but if we wer
Hello Zeev,
yeah! which is why there is no need to do anything on that front :-)
marcus
Friday, March 10, 2006, 12:26:20 AM, you wrote:
> No speed boost with opcode caches, which will be bundled in PHP 6 :)
> Zeev
> At 01:15 10/03/2006, Marcus Boerger wrote:
>>Hello Sara,
>>
>> but if we
1 - 100 of 115 matches
Mail list logo
