Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25968 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44934 invoked by uid 1010); 6 Oct 2006 16:17:21 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 44919 invoked from network); 6 Oct 2006 16:17:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2006 16:17:21 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 80.74.107.235 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from [80.74.107.235] ([80.74.107.235:1391] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/D5-11652-C8186254 for ; Fri, 06 Oct 2006 12:17:21 -0400 Received: (qmail 19858 invoked from network); 6 Oct 2006 16:15:53 -0000 Received: from office.zend.office (HELO ?192.168.16.109?) (192.168.16.109) by internal.zend.office with SMTP; 6 Oct 2006 16:15:53 -0000 Message-ID: <45268186.5050008@zend.com> Date: Fri, 06 Oct 2006 09:17:10 -0700 Organization: Zend Technologies User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Ilia Alshanetsky CC: internals@lists.php.net References: <50.8B.48579.ED205254@pb1.pair.com> <45252FC7.9030500@php.net> <4e89b4260610060728v51b1ba65m69304a88d693ce7d@mail.gmail.com> <45267188.9030107@emini.dk> <45267B7D.9080206@zend.com> <45267C07.3090404@emini.dk> <45267D5A.70401@emini.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: [VOTE] Intermediate Results From: stas@zend.com (Stanislav Malyshev) > I be wary of allowing this because in some instances method signature > can drastically impact behavior for example > foo(&$bar) {} vs foo($bar); I'd prefer to don't reduce this to E_NOTICE. Yes, it can have runtime impact. So what? There are so many cases where, for example, not declaring a variable upfront or not assigning a type to it may change script behavior and even introduce a security hole. However, PHP is built to allow such things, and I do not think we should prohibit them - especially if there are a lot of valid uses for them. I think PHP should have priority on flexibility over strictness, if you prefer strict language you can always have Java and declare everything up to the last bit :) > You are talking about creating static class variables (dynamic ones can > already be created without even an E_NOTICE). I think if you need this > done, why not create a property dynamically and then access it > statically? I suppose you are using this is a means of having a global What do you mean by "creating dynamically and accessing statically"?