Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:16040
Return-Path: <cellog@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 63397 invoked by uid 1010); 20 Apr 2005 03:11:52 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 63331 invoked by uid 1007); 20 Apr 2005 03:11:50 -0000
Message-ID: <20050420031150.63328.qmail@lists.php.net>
To: internals@lists.php.net
Date: Tue, 19 Apr 2005 23:11:46 -0400
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 66.65.39.8
Subject: protected/private function __construct() not allowed in 5.0.4?
From: cellog@php.net (Greg Beaver)

Hi all,

I just spent quite a while searching the archives, and can't find any 
explanation of why this code worked in 5.0.3 but doesn't in 5.0.4:

<?php
class blah {
     protected function __construct(){}
}
?>

Could someone please enlighten me?  I was using this for a singleton 
pattern, and so it would be nice to know why it is so critical for the 
engine to be anal retentive here.  It seems to me that it should be up 
to the programmer to decide how easily the object can be instantiated, 
unless there is a deeper engine stability issue.

Thanks,
Greg