On Tue, Jul 12, 2011 at 01:28, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 4:20 PM, Kalle Sommer Nielsen wrote:
>>
>> I agree, it would make more sense to have the votings over before
>> doing the next Alpha, so theres time to cook up relevant patches and
>> commit them.
>
> Well, OK, let's say we d
On Mon, 11 Jul 2011 22:33:31 +0100, Paul Dixon wrote:
> personally long term, I would aim to remove the position index entries
> completely.
Which would make it unusable with list().
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.ph
On Sun, 2011-07-10 at 19:41 +0200, Nikita Popov wrote:
> E.g. Writing
>
> class Evaluator {
> public function eval() {
>
> }
> }
>
> Does in no way create an ambiguity with the eval language construct PHP
> implements.
For a method this is correct. But for a normal function this is
diff
hi,
As of now I do not think we should allow this change, whether the RFC
is accepted or not does not matter as it will badly break BC. Unless
there is a patch allowing this change without affecting existing code
(main point being namespaced code working smoothly), this RFC should
be rejected.
Ch
2011/7/12 Michael Wallner :
> On Mon, 11 Jul 2011 22:33:31 +0100, Paul Dixon wrote:
>> personally long term, I would aim to remove the position index entries
>> completely.
>
> Which would make it unusable with list().
>
+1 this will be huge BC break for this function. Please, don't remove
positio
On 12/07/11 11:09, Pierre Joye wrote:
hi,
Hi,
As of now I do not think we should allow this change, whether the RFC
is accepted or not does not matter as it will badly break BC. Unless
there is a patch allowing this change without affecting existing code
(main point being namespaced code worki
>
> PS: I cannot change my vote on https://wiki.php.net/todo/php54/vote, is it a
> known issue?
>
if you don't have @php.net account, or 'voting' group membership in
the wiki, then you cannot vote, or change your vote.
this change was made yesterday to fix the issue that the technical
restriction
On 12/07/11 12:12, Ferenc Kovacs wrote:
PS: I cannot change my vote on https://wiki.php.net/todo/php54/vote, is it a
known issue?
if you don't have @php.net account, or 'voting' group membership in
the wiki, then you cannot vote, or change your vote.
this change was made yesterday to fix the is
Zitat von Pierre Joye :
On Mon, Jul 11, 2011 at 10:15 AM, Jan Schneider wrote:
Zitat von Ferenc Kovacs :
On Sun, Jul 10, 2011 at 11:17 PM, Pierre Joye
wrote:
hi,
As I could agree on this fact, I can't find any existing project
having int(eger), float&co as class, namespaced or not. Do
Hi,
On Tue, 12 Jul 2011 11:09:33 +0200, Pierre Joye wrote:
> As of now I do not think we should allow this change, whether the RFC is
> accepted or not does not matter as it will badly break BC. Unless there
> is a patch allowing this change without affecting existing code (main
> point being nam
On 2011-07-12, Johannes Schlüter wrote:
> On Sun, 2011-07-10 at 19:41 +0200, Nikita Popov wrote:
> > E.g. Writing
> >
> > class Evaluator {
> > public function eval() {
> >
> > }
> > }
> >
> > Does in no way create an ambiguity with the eval language construct
> > PHP implements.
>
> Fo
On 2011-07-12, Pierre Joye wrote:
> hi,
>
> As of now I do not think we should allow this change, whether the RFC
> is accepted or not does not matter as it will badly break BC. Unless
> there is a patch allowing this change without affecting existing code
> (main point being namespaced code worki
Hi guys,
there is an open bug (https://bugs.php.net/bug.php?id=54488) which
seems only to be triggered when using FPM: a segfault in
zend_assign_to_variable.
My knowledge of Zend internal stuff is limited and I really don't know
how this can be related to FPM. If someone have time to look at it
w
13 matches
Mail list logo
