Thank you Lukas.
Mark Tinsley
Developer
Dallas Airmotive
(214) 353-6739
[EMAIL PROTECTED]
-Original Message-
From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 9:51 AM
To: Marcus Boerger
Cc: Tinsley, Mark; internals@lists.php.net
Subject: Re: [PHP-DEV
On 20.06.2008, at 16:28, Marcus Boerger wrote:
Hello Mark,
we discussed overloading a hell lot of times an dthe conclusionj
always
and every single time has been NO. It would mean a large slowdown for
every single PHP application out there and it is not really that much
halpful. In fact it
ailto:[EMAIL PROTECTED]
> Sent: Thursday, June 19, 2008 11:12 AM
> To: internals Mailing List
> Subject: Re: [PHP-DEV] Overloading
> I'm developing a PHP framework and had the same issue sometimes... I
> think
> it was already discussed in the list, did you searched the archi
ee it as a very
helpful addition and can't see a reason why we could not add it.
Mark
-Original Message-
From: Saulo Vallory [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 19, 2008 11:12 AM
To: internals Mailing List
Subject: Re: [PHP-DEV] Overloading
I'm developing a PHP framewo
I'm developing a PHP framework and had the same issue sometimes... I think
it was already discussed in the list, did you searched the archives?
Saulo
On Thu, Jun 19, 2008 at 9:58 AM, Tinsley, Mark <[EMAIL PROTECTED]>
wrote:
> What about the addition of overloading for PHP 6?
>
> I am not totally
What about the addition of overloading for PHP 6?
I am not totally up to date on the developments of the parameter type
hints. I briefly read the meeting minutes for PHP 6.
What about with the type hints we have now?
class moo
{
public static function foo(FooClass $FooVar)
{
//
Hi!
the proposal is not yet ready, so there can't be a decision or valuable
discussion at this point. Please leave me some time to finish it :)
OK, no problem. I was just surprised it's being discussed, and yet in
non-related topic :)
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PRO
Hi Marcus (and Sara):
On Sun, May 25, 2008 at 06:48:48PM +0200, Marcus Boerger wrote:
>
> That said there is a bug in __callStatic which we need to
> report and assign to Sara.
http://bugs.php.net/bug.php?id=45089
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P
Hi Daniel,
On Sat, Apr 05, 2008 at 09:27:33AM -0400, Daniel Convissor wrote:
> * The new __callStatic() is neat. Thanks. Is there consideration of
> adding Static versions of the other overloading methods?
It is part of the proposal for real static classes
(http://wiki.php.net/rfc/static-class
Hello Daniel,
Sunday, May 25, 2008, 4:30:32 PM, you wrote:
> Hi Marcus:
> On Sun, May 25, 2008 at 10:57:22AM +0200, Marcus Boerger wrote:
>> Saturday, April 5, 2008, 3:27:33 PM, you wrote:
>>
>> We experimented with visibility and ran into trouble.
> ...
>> So we in fact note the visibility but
Hi Marcus:
On Sun, May 25, 2008 at 10:57:22AM +0200, Marcus Boerger wrote:
> Saturday, April 5, 2008, 3:27:33 PM, you wrote:
>
> We experimented with visibility and ran into trouble.
...
> So we in fact note the visibility but then ignore it.
>
> I think we either need to respect the visibility
Hello Daniel,
Saturday, April 5, 2008, 3:27:33 PM, you wrote:
> [Hmm... No answer in several days. Let's try this again with a
> different subject]
> I'm in the middle of clarifying the Overloading section of the manual,
> http://docs.php.net/manual/en/language.oop5.overloading.php. Some issu
[Hmm... No answer in several days. Let's try this again with a
different subject]
I'm in the middle of clarifying the Overloading section of the manual,
http://docs.php.net/manual/en/language.oop5.overloading.php. Some issues
and questions have come up and your insights will be helpful, please
I'm in the middle of clarifying the Overloading section of the manual,
http://docs.php.net/manual/en/language.oop5.overloading.php. Some issues
and questions have come up and your insights will be helpful, please.
* The docs say "All overloading methods must be defined as public." At
this poin
Hello!
Trying to use ZE2's new features for my framework I fell in trouble with
(probably) abnormal behaviour of overloaded class properties which has been
declared as "expected" long time ago.
First of all, I do admit this feature has been discussed before, but despite
of all that I apologize fo
15 matches
Mail list logo
