Req #33698 [Com]: Conflicts with multiple interfaces sharing common method names

From: Date: Thu, 10 Nov 2011 12:09:45 +0000
Subject: Req #33698 [Com]: Conflicts with multiple interfaces sharing common method names
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-165009@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=33698&edit=1

 ID:                 33698
 Comment by:         arkadiusz dot robinski at allegro dot pl
 Reported by:        jason at hybd dot net
 Summary:            Conflicts with multiple interfaces sharing common
                     method names
 Status:             Suspended
 Type:               Feature/Change Request
 Package:            Feature/Change Request
 Operating System:   *
 PHP Version:        5.0.4
 Block user comment: N
 Private report:     N

 New Comment:

I also encountered this problem. I agree with mail at rones dot de. It is very annoying if you want
to implement interfaces from different 3rd party components. Current behaviour should be changed.


Previous Comments:
------------------------------------------------------------------------
[2009-01-28 13:54:57] lukasz dot wojciechowski at ngsoft dot pl

I just run into this problem and I decided to post a comment to bring attention to this issue.

--
Best regards
£ukasz Wojciechowski

------------------------------------------------------------------------
[2007-02-01 09:48:19] mail at rones dot de

Is there someone thinking (or even working) on this issue? It is really important if you want to use
different 3rd party components which provides interfaces you have to implement to use the components
and there exists some methods _with the same signature_ more than once. In case of different
signatures I can understand there would occur problems because PHP does not have an method
overloading possibility yet.

------------------------------------------------------------------------
[2005-07-15 14:13:13] wez@php.net

FWIW, I agree; I think our interface support is pretty crappy because of this.

I'm changing this to suspended status, because maybe one day it will appear, it's just not
possible at the moment.


------------------------------------------------------------------------
[2005-07-15 13:57:10] jason at hybd dot net

I know PHP != Java, but surely this sort of stuff should be documented? Most people will expect
interfaces to work like Java interfaces or C++ "interfaces" (Pure virtual abstract
methods), as many other languages seem to follow this behaviour. As I said this is debatable as it
depends how you look at things, and likewise it is fairly easy to work round this issue.

------------------------------------------------------------------------
[2005-07-15 12:44:04] sniper@php.net

PHP != Java

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=33698


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=33698&edit=1


Thread (9 messages)

« previous php.bugs (#165009) next »