Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41720 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99060 invoked from network); 6 Nov 2008 12:32:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2008 12:32:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=steph@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=steph@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.164 as permitted sender) X-PHP-List-Original-Sender: steph@php.net X-Host-Fingerprint: 64.99.136.164 smtprelay-virgin0164.hostedemail.com Received: from [64.99.136.164] ([64.99.136.164:54237] helo=smtprelay-virgin.hostedemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 63/1D-35522-BC3E2194 for ; Thu, 06 Nov 2008 07:32:11 -0500 Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay05.hostedemail.com (Postfix) with SMTP id 8C0E2E3CB20; Thu, 6 Nov 2008 12:32:07 +0000 (UTC) X-SpamScore: 1 X-Spam-Summary: 2,0,0,1ee3ce7a9bd47d45,691ff1dea13fdf9b,steph@php.net,iammrdan@googlemail.com:internals@lists.php.net,RULES_HIT:355:379:539:540:541:542:543:567:599:601:982:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1515:1516:1518:1534:1541:1587:1593:1594:1711:1730:1747:1766:1792:2073:2075:2078:2198:2199:2393:2553:2559:2562:2693:2736:2828:3027:3352:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:3876:3877:4250:5007:6114:6119:6261:7653:7875:7903:8501,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none Received: from foxbox (62-31-252-63.cable.ubr07.shef.blueyonder.co.uk [62.31.252.63]) (Authenticated sender: steph.fox) by omf09.hostedemail.com (Postfix) with ESMTP; Thu, 6 Nov 2008 12:32:06 +0000 (UTC) Message-ID: <015801c9400b$f227ead0$3ffc1f3e@foxbox> To: "Dan" Cc: References: <4EA88C3A8A2747989925A5D21448FCE7@pc> <200811052154.29537.larry@garfieldtech.com> <98b8086f0811060150p2fb0312dj66896cb227c871ec@mail.gmail.com> <007301c93ffe$f4b5ad80$3ffc1f3e@foxbox> <029101c94004$d4564440$7d02ccc0$@com> <013b01c94007$b66d60a0$3ffc1f3e@foxbox> Date: Thu, 6 Nov 2008 12:33:59 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-session-marker: 73746570682E666F78 Subject: Re: [PHP-DEV] Call it: allow reserved words in a class or not? From: steph@php.net ("Steph Fox") Dan, > PHP may be a hybrid language, but the fact is you're implementing object > oriented functionality, and as such should be implementing it in a way > that > follows de-facto standards in object oriented language design. I should be > able to overload your internal array object, and yes, arraysshould be > objects. I'm really confused as to why you'd want to overload something that doesn't exist. Can't we just deal with reality here? Several million PHP scripts written over the last decade will still able to run without change under PHP 5.3. Several PHP developers are not OO programmers and some - maybe even most - never will be. Don't you think that suddenly turning arrays into objects might cause just the teeniest bit of a problem here? > Javascript would be a prime example of a non-standard object oriented > approach, and yet that still manages to support the basics in a way that > make sense. Great, so drop PHP and go use Javascript. Oh wait - you can't. Because *it wasn't designed do the same job*. - Steph