Re: Re: declaring classes as static or final

From: Date: Tue, 28 Sep 2004 21:32:04 +0000
Subject: Re: Re: declaring classes as static or final
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-13060@lists.php.net to get a copy of this message
Hello Michael, Tuesday, September 28, 2004, 3:44:48 PM, you wrote: > things i'd like to add: > 2. final classes: > final classes can't be extended already supported > 4. abstract classes can be defined static also makes no sense (duplicate): both mean you cannot instantiate the class. > <?php > abstract static class foo { > abstract public static function bar(); > } abstract static methods are already supported > this means that all subclasses of foo must also be static and can only > contain static methods and attributes > 5. abstract classes can't be defined final already supported static classes would be implementable at the cost of increasing compiler time. To decide whether to think more about it we'd to know a case where you need such syntax, what you win by having it and what you loose if you don't have it. regards marcus p.s.: as a hint, next time read the docs before requesting syntax we support already.

« previous php.internals (#13060) next »