Bug #40880 [Com]: public->protected inheritance causes fatal

From: Date: Sun, 06 May 2012 15:40:27 +0000
Subject: Bug #40880 [Com]: public->protected inheritance causes fatal
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-170262@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=40880&edit=1

 ID:                 40880
 Comment by:         ekincigokan at gmail dot com
 Reported by:        prometheus__0 at hotmail dot com
 Summary:            public->protected inheritance causes fatal
 Status:             Not a bug
 Type:               Bug
 Package:            Class/Object related
 Operating System:   SUSE SLES 10
 PHP Version:        5CVS-2007-03-21 (snap)
 Block user comment: N
 Private report:     N

 New Comment:

Same "problem".

class A{
    public function __construct(){}
}

class B extends A {
    protected function __construct(){}
}

Please, can you tell us a reason why we can't put an private/protected access to B's
constructor if A's constructor is public ?
Is there any logical reason to this ?


Thanks.


Previous Comments:
------------------------------------------------------------------------
[2011-09-10 22:27:24] herman dot wetherington at gmail dot com

Apparently, we don't call this a "bug" because this is not caused by a programming
error. So I'm calling it a "massive design flaw" instead.

------------------------------------------------------------------------
[2010-10-15 23:33:35] robertoblanko at gmail dot com

Same problem here. You cannot actually apply the singleton pattern to subclasses with this behavior.
I do not see any reason for not calling this a bug.

------------------------------------------------------------------------
[2010-09-07 12:58:35] nickyla83 at yahoo dot fr

I'm in the same situation as our friend "prometheus" here, I am trying to use a
singleton pattern and logically, this should involve being able to encapsulate the subcalasses
information particularly setting up a private constructor for the singleton subclass, IT DEFINITELY
DOES MAKE SENSE, so please try to take this under consideration for the next php engine release.

------------------------------------------------------------------------
[2007-03-21 10:05:25] prometheus__0 at hotmail dot com

is this the 'php'-dev definition?
i'm asking cause wraping a singleton pattern around a subclass makes sense
and the same example is valid for java and c++
to ask it differently: why is it working this way in php? (i'm interested in the background of
this)
my point is that 2 languages allow it and there is an example which is valid, not?

------------------------------------------------------------------------
[2007-03-21 09:43:47] derick@php.net

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php

This is how it works... you can always open up an API through a new extended interface, but not hide
more.

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


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=40880


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


Thread (13 messages)

« previous php.bugs (#170262) next »