Re: [RFC] Static classes (Was Abstract final classes)
| From: | Levi Morrison | Date: | Mon, 01 Dec 2014 17:58:29 +0000 |
| Subject: | Re: [RFC] Static classes (Was Abstract final classes) | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-79346@lists.php.net to get a copy of this message | ||
> The only thing missing is a standardised, enforced, annotation on the class
> to declare that you are using this ability and instances will never be
> created.
Let's say a class has no members: what's the harm in instantiating it?
Sure, it logically doesn't do anything useful, but is this user error
such a big deal that we alter the language to disallow it?