2009/9/19 Carsten Wiedmann carsten_st...@gmx.de
Kalle Sommer Nielsen schrieb:
2009/9/19 Carsten Wiedmann carsten_st...@gmx.de:
So that's the next PHP release with a broken IPv6 support (after 5.2.10 and
5.3.0) and so it's not possible to update for some peoples.
Is there a bug # on
Hi all,
Is there an effort underway to move POSIX regexps to PECL? If not,
should there be? We have some people freaking out (some who don't
appear to know about PCRE, but some who do have codebases using ereg*).
However, after reading various PHP internals meeting minutes etc I
don't know
I, for one, am quite happy that it's fairly complicated and convoluted
to get the caller of a method, since it could lead to some seriously
incomprehensible code in the hands of someone who don't know what they
are doing. Requiring the user to use the backtrace is a clear warning
sign, and I
hi,
On Sat, Sep 19, 2009 at 2:47 AM, Carsten Wiedmann carsten_st...@gmx.de wrote:
Ilia Alshanetsky schrieb:
The PHP development team would like to announce the immediate
availability of PHP 5.2.11. ... All users of PHP 5.2 are encouraged to
upgrade to this release.
So that's the next PHP
ah misread, I first thought it was
That's not something we can fix as far as I can tell. But please open
a bug for this issue with:
- windows version used for the tests
- which last PHP version works as you expected
Cheers,
On Sat, Sep 19, 2009 at 12:44 PM, Pierre Joye pierre@gmail.com
-Original Message-
From: Stan Vassilev [mailto:sv_for...@fmethod.com]
Sent: 19 September 2009 11:33
To: troels knak-nielsen; Ford, Mike
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] reference caller object
I, for one, am quite happy that it's fairly complicated and
Okay, that gets me thinking.
First of all, we still would need to decide if the language should
withhold a feature to help the users. It's really up to them how
they use this basic reference. You've brought up a good point, but
surely there are certain situations... Unless...
We can
I guess what I'm really getting at is another access modifier:
private, protected, public...
And now adding something like trusted.
trusted function myMethod() callable trustedInterface {}
In a case like this, caller would always be available, but not always
type-checked.
Chris Trahey
Web
hi Johannes,
It is a really great improvement that we don't have to worry anymore
about being in a release phase for a given branch. However one thing I
would like to improve in the merge frequency. Having a large merge the
day (or the day before) a RC does not sound too god to me. It would be
W liście Chris Trahey z dnia sobota 19 września 2009:
I guess what I'm really getting at is another access modifier:
private, protected, public...
And now adding something like trusted.
trusted function myMethod() callable trustedInterface {}
In a case like this, caller would always be
On Friday 18 September 2009 11:36:08 pm Chris Trahey wrote:
Hey all, thanks for the discussion.
First, in terms of implimentation, I've gone back and forth between a
few ways to expose it, but it struck me tonight that the most similar
keyword in use currently is $this. Next to that I think
There are patterns that would be violated by using a caller reference,
but none that would be broken by having one. Each development team can
decide what features to use.
With regard to friend classes, I'll start a new thread since it is a
fundamentally different subject.
For this
Request for comments/thoughts:
A new access modifier for methods (members as well, I guess) to allow
access only from certain classes/interfaces.
Call it whatever (group, trusted, party, etc), but perhaps something
like this:
group function myMethod($arg) accessible MyInterface MyClass {}
13 matches
Mail list logo
