Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65525 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70446 invoked from network); 31 Jan 2013 03:20:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jan 2013 03:20:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=truth@proposaltech.com; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=truth@proposaltech.com; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain proposaltech.com does not designate 98.139.44.129 as permitted sender) X-PHP-List-Original-Sender: truth@proposaltech.com X-Host-Fingerprint: 98.139.44.129 nm2.access.bullet.mail.sp2.yahoo.com Received: from [98.139.44.129] ([98.139.44.129:32928] helo=nm2.access.bullet.mail.sp2.yahoo.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2D/2D-09318-DF2E9015 for ; Wed, 30 Jan 2013 22:20:29 -0500 Received: from [98.139.44.107] by nm2.access.bullet.mail.sp2.yahoo.com with NNFMP; 31 Jan 2013 03:20:26 -0000 Received: from [67.195.22.117] by tm12.access.bullet.mail.sp2.yahoo.com with NNFMP; 31 Jan 2013 03:20:26 -0000 Received: from [127.0.0.1] by smtp112.sbc.mail.gq1.yahoo.com with NNFMP; 31 Jan 2013 03:20:26 -0000 X-Yahoo-Newman-Id: 680917.99345.bm@smtp112.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: tLSxkY8VM1lgsC59ZqEInC1w7AhSxK_3qnqsJuJslPpUQ7M d_PSr3PcRlSbY4wpcRxb7tFjbcjdpmHNv_y5cr4ku_Nbdx8.BdaG3iGFHxEG reaUg_zj1ANVG3GeFjB_fgbIHorWvjDTrA3rQHZconzQSuyaMH2.vUTe1T3N 3_IOuAAiCFITyUlFJPVi0q8y4_7161bDqyQ6wGiT3gnOjyN.Abz4._xB_SnW 0QpiDihr4XXZQacPagaTx6Umj2lggjfUQNXUB4ow3xYe0fr2pmQz6sWbIA36 izhxP0xB6zr250JisDUviXuhehSI06K7C6dhOqIMRpDgGzYWEbxhdFhrMryR 2ri80VybodL_P8AMD4ZoGMuyy8pgrH4fCW4CyxxcIm7Z.Cv_gHVEbCedy5lF ewnpwQKnk6rvhxZfTq22UABl5_xAa1p8_VZ_tvQL3B3.anFNoeIy4extZFPb i411pRGkNyVkIU4qGPoIFzOI2Spe3Atj4snpXO5Xxkw-- X-Yahoo-SMTP: jWG9jiaswBBOCHlPTWD9zJWRnNyiDJE- Received: from [192.168.2.102] (truth@70.230.192.99 with login) by smtp112.sbc.mail.gq1.yahoo.com with SMTP; 30 Jan 2013 19:20:26 -0800 PST To: PHP Internals In-Reply-To: <5109CC1F.3070507@roojs.com> References: <1460659e-237d-4c7c-8cfa-523ec857d646@email.android.com> <51074873.5090600@roojs.com> <51076233.2040507@sugarcrm.com> <5109A834.6070503@roojs.com> <5109B421.4000805@sugarcrm.com> <5109CC1F.3070507@roojs.com> Content-Type: text/plain; charset="ISO-8859-1" Date: Wed, 30 Jan 2013 19:20:25 -0800 Message-ID: <1359602425.11156.416.camel@inspiron> Mime-Version: 1.0 X-Mailer: Evolution 2.30.1.2 Content-Transfer-Encoding: 7bit Subject: Re: Deprecate and remove calls from incompatible context From: truth@proposaltech.com (Todd Ruth) Some of us have rather large bodies of code written over 10-12 years that make significant use of calling $this from "incompatible contexts" (i.e. we know it's compatible, but php doesn't). Most consider such use a sin. Could there be a compromise that would allow us evildoers to continue in our evil ways without identifying and changing every use? Perhaps "implements allowStaticCallsFromIncompatibleContexts" or somesuch? I can imagine replacing every "class ..." with "class ... implements ...", but identifying and changing every place we use an incompatible context will be very, very unpleasant. We can figure out the places that are hit most frequently using the logs, but that isn't necessarily a complete list. If this were a security issue, I'd understand making everyone go through the pain. The RFC indicates the rationale is helping users find bugs. It would be nice if those of us who would rather avoid a BC break than easily find those bugs could do so. Thanks for your consideration. - Todd