Bug #68698 [Com]: Fatal error cannot redeclare [class not being redeclared]

From: Date: Mon, 15 Mar 2021 07:00:38 +0000
Subject: Bug #68698 [Com]: Fatal error cannot redeclare [class not being redeclared]
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-232714@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=68698&edit=1

 ID:                 68698
 Comment by:         modelmonikasharma at gmail dot com
 Reported by:        pegasus at vaultwiki dot org
 Summary:            Fatal error cannot redeclare [class not being
                     redeclared]
 Status:             No Feedback
 Type:               Bug
 Package:            Scripting Engine problem
 Operating System:   Centos 6 64-bit
 PHP Version:        5.6Git-2014-12-30 (Git)
 Block user comment: N
 Private report:     N

 New Comment:

I Don't thing anyone write better that this. Amazing Post!! Keep it up!
<a href="https://www.aarinkaur.com/">Mumbai
Escorts</a>
<a href="https://www.aarinkaur.com/">Escorts
Mumbai</a>


Previous Comments:
------------------------------------------------------------------------
[2016-03-16 11:40:33] loebert at netfeld dot de

Found this bug active on debian jessie with PHP Version 5.6.17
Try this little code:

class c2 extends c1
{
    function demo(){
        print("Child");
    }
}

class c1{
    function demo(){
        print("Mother");
    }
}


$demo=new c2();
$demo->demo();

When calling this code twice (!) - you will get the error. And then change position of c2 and c1: no
problems any more.

------------------------------------------------------------------------
[2015-11-04 13:25:29] info at interpost dot biz

I have had this fatal error: Cannot redeclare class ... from PHP 5.6.12 through to and including
5.6.14 on Debian Jessie.  It prevents horde (webmail) admin configuration pages from loading
properly (chrome gives an ERROR_EMPTY_RESPONSE error, and firefox states that the connection was
reset while the page wes loading) - same result no page. This error currently prevents a drupal 7.41
admin page from activating or or disabling modules. So this problem is still there. Is it a bug, or
a change in PHP's requirements that developers of other software need to re-code to make their
code compliant?

------------------------------------------------------------------------
[2015-03-21 13:28:49] pegasus at vaultwiki dot org

I am no longer experiencing this issue as of #d092cb6

------------------------------------------------------------------------
[2015-02-01 04:22:15] php-bugs at lists dot php dot net

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.

------------------------------------------------------------------------
[2015-01-23 19:54:45] aharvey@php.net

--disable-opcache should do it, or alternatively, you can just not load the extension in your
php.ini (since it's not built into PHP).

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


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


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


Thread (17 messages)

« previous php.bugs (#232714) next »