Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55475 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75740 invoked from network); 17 Sep 2011 13:27:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Sep 2011 13:27:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: rquadling@gmail.com X-Host-Fingerprint: 209.85.216.170 mail-qy0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:42758] helo=mail-qy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/50-05466-B50A47E4 for ; Sat, 17 Sep 2011 09:27:56 -0400 Received: by qyl16 with SMTP id 16so1178712qyl.8 for ; Sat, 17 Sep 2011 06:27:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:from:date:message-id:subject:to:content-type; bh=O7OIj8ouCcPMtzGQsP1lHRxXO22qUg0uyPx+7KMnYxU=; b=bm8oYILs4vIFSyhYXDmYDz9LB/MvVmIYsIFCaOHAUJiR0O4EHEwdFT1qLLWL9DYHC5 UugdXC3ZUmh/E4iLQ1wT/l26TdM6mv++mcDpbuDp285us0DjvfcB4Sdaa3eTXwUPcYO8 9ineXGEb+l9mcDcJW4wNuSKA5Zd2z9b2UfWdw= Received: by 10.229.242.7 with SMTP id lg7mr422919qcb.28.1316266073112; Sat, 17 Sep 2011 06:27:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.53.193 with HTTP; Sat, 17 Sep 2011 06:27:33 -0700 (PDT) Reply-To: RQuadling@GMail.com Date: Sat, 17 Sep 2011 14:27:33 +0100 Message-ID: To: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: __constructor parameter limitations. From: rquadling@gmail.com (Richard Quadling) Hi. With the recent BC with regard the locking of the constructor's signature for subclasses, what is the expected mechanism for allowing a subclass to have additional parameters? You can always supply them and use func_get_args() / func_num_args() / etc. to read them. It would seem that the limitation restricts the capabilities. I'm not a purist. Software development is a compromise between purity and getting the job done in an efficient and understandable manner. By allowing undocumented parameters to the constructor (due to the enforced signature), this would seem to break things on a different front (I can't docblock non defined parameters for examples). Richard. -- Richard Quadling Twitter : EE : Zend : PHPDoc @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea