abstract private methods

20 years ago by Stanislav Malyshev — view source — reply

unread

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
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

20 years ago by John LeSueur — view source — reply

unread

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 to reserve a function for future use?

John LeSueur

20 years ago by Stanislav Malyshev — view source — reply

unread

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
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

20 years ago by John Coggeshall — view source — reply

unread

Sure, except you can't create an instance of a class which contains
abstract methods.

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 to reserve a function for future use?

John LeSueur

20 years ago by Andi Gutmans — view source — reply

unread

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") but maybe I am
not seeing some use for it.

Stanislav Malyshev, Zend Products Engineer
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

20 years ago by Sebastian Bergmann — view source — reply

unread

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 http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69

20 years ago by Stanislav Malyshev — view source — reply

unread

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 different
JL>>function name.

How would he? Private methods by definition can't be seen by child
classes, so whatever you do with private methods would have no influence
on inheriting class. That's the whole point in it, why I think it's of no
use - because you can't meaningfully both require override (abstract) and
hide from inherited classes (private).

--
Stanislav Malyshev, Zend Products Engineer
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

20 years ago by nicobn@gmail.com — view source — reply

unread

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 functions use them "from the inside"
(self::PrivateFunction()) without the class being actually declared,
as in my case.

Just my 2 cents

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 different
JL>>function name.

How would he? Private methods by definition can't be seen by child
classes, so whatever you do with private methods would have no influence
on inheriting class. That's the whole point in it, why I think it's of no
use - because you can't meaningfully both require override (abstract) and
hide from inherited classes (private).

--
Stanislav Malyshev, Zend Products Engineer
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

20 years ago by Marcus Boerger — view source — reply

unread

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 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 functions use them "from the inside"
(self::PrivateFunction()) without the class being actually declared,
as in my case.

Just my 2 cents

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 different
JL>>function name.

How would he? Private methods by definition can't be seen by child
classes, so whatever you do with private methods would have no influence
on inheriting class. That's the whole point in it, why I think it's of no
use - because you can't meaningfully both require override (abstract) and
hide from inherited classes (private).

--
Stanislav Malyshev, Zend Products Engineer
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

--

--

--
Best regards,
Marcus mailto:mail@marcus-boerger.de

abstract private methods

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.

I'm not quite understanding this concept - if you can't use it in the code in no way, why declare it at all?

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.

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.

I'm not quite understanding this concept - if you can't use it in the
code in no way, why declare it at all?

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.