As of now, PHP allows declaring abstract private methods. Does anyone has
any use for it? IMO, it is meaningless and should be disallowed (basically
it just says "this method does not exist and never will") but maybe I am
not seeing some use for it.
--
Stanislav Malyshev, Zend Products Engineer
Stanislav Malyshev wrote:
As of now, PHP allows declaring abstract private methods. Does anyone
has any use for it? IMO, it is meaningless and should be disallowed
(basically it just says "this method does not exist and never will")
but maybe I am not seeing some use for it.
It can be used t
JL>>It can be used to reserve a function for future use?
I'm not quite understanding this concept - if you can't use it in the
code in no way, why declare it at all?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115
--
PHP Internal
Sure, except you can't create an instance of a class which contains
abstract methods.
On Wed, 2005-06-08 at 12:40 -0600, John LeSueur wrote:
> Stanislav Malyshev wrote:
>
> > As of now, PHP allows declaring abstract private methods. Does anyone
> > has any use for it? IMO, it is meaningless and
Nope, I don't see any use for that.
At 09:29 PM 6/8/2005 +0300, Stanislav Malyshev wrote:
As of now, PHP allows declaring abstract private methods. Does anyone has
any use for it? IMO, it is meaningless and should be disallowed (basically
it just says "this method does not exist and never will"
Stanislav Malyshev wrote:
> As of now, PHP allows declaring abstract private methods. Does anyone
> has any use for it?
I do not see a use for this and I think it should be disallowed;
abstract methods only make sense when declared public or protected.
--
Sebastian Bergmann
JL>>some of them yet, but I release this code to be used. Someone comes along
JL>>and extends my class. If I have these future planned functions in as
JL>>abstract private, then they are protected for my future use in the base
JL>>class. The user extending my class will realize he needs to use a di
For my part, I use abstract classes as routines libraries. That is,
instead of having tons of functions lying freely outside of any
classes, I use classifications. Each class represents a type a
categorie of action.
The whole point of having private functions in abstract classes is
when public fun
Hello Nicolas,
you didn't read carefully we weren't talking aabout
abstarct class cname{ private function fname() }
but instead of
class cname { abstract private function fname() }
or
interface cname { private function fname() }
Friday, June 10, 2005, 12:04:43 AM, you wrote:
> For my part, I u
