Hello,
First, to be clear, you're mixing two kinds of static keywords:
1) a static method/property which represents a method/property that is bound
to a class only
2) the "static" class reference
Of course, private properties (static or not) are not accessible from any
other scope than the one in
Hello all,
I'm playing around with 5.3, and I noticed the following interesting behavior:
class A
{
private static $cls = __CLASS__;
public static function who()
{
print static::$cls;
}
}
class B extends A
{
private static $cls = __CLASS__;
}
B::who(); // Fatal
Hi Derick, That was very quick, Thank you. I have committed the tests now.
regards,
Raghubansh
On Dec 14, 2007 9:44 PM, Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Fri, 14 Dec 2007, Raghubansh wrote:
>
> > kraghuba
>
> okay, I upgraded you.
>
> regards,
> Derick
>
--
with Regards,
Raghuba
Attached is the proof-of-concept patch. If the idea is met well, then
I'll keep working on it to add caching and, if there's interest, I'll
add *namespace imports*.
An example of how a class in a namespace that's named the same as an
internal class can be loaded:
autoload.php
include_onc
On Fri, 14 Dec 2007, Raghubansh wrote:
> kraghuba
okay, I upgraded you.
regards,
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 14 Dec 2007, Raghubansh wrote:
> Would it be possible to upgrade me so that i can commit these tests.
> I have been writing & committing phpt testcases for testing strings, arrays,
> files, etc functions.
What's your CVS id?
regards,
Derick
--
PHP Internals - PHP Runtime Development Ma
Hi,
I started looking at coverage of the ext/tokenizer this week. I
tried to commit testcases related to token_get_all() today but looks
like my CVS ID doesn't let me commit to ext/tokenizer. The pre-commit
check fails, looks like i do not access.
Would it be possible to upgrade me so that i ca
Hello!
As we all know, PHP 4's general releases will stop being made at the end
of the year. We've two weeks until then, and I think it'd be a good idea
to wrap all latest fixes up into PHP 4.4.8. I am planning an RC for next
thursday - unless somebody has a strong argument against this.
regar
Hi all,
Having spent a few hours tussling with the load-order bogey, I found what I
think is a bit of a gap in the win32 build process.
There are no configure warnings at all when there's a missing extension
dependency... only a bailout if you try to build a dependency as shared for
a static
