Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38616 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55168 invoked from network); 25 Jun 2008 15:06:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jun 2008 15:06:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=MTinsley@dallasairmotive.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=MTinsley@dallasairmotive.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain dallasairmotive.com from 66.138.198.142 cause and error) X-PHP-List-Original-Sender: MTinsley@dallasairmotive.com X-Host-Fingerprint: 66.138.198.142 66-138-198-142.dallasairmotive.com Windows 2000 SP4, XP SP1 Received: from [66.138.198.142] ([66.138.198.142:4080] helo=svr-fp-exch.dalair.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/96-20985-8EE52684 for ; Wed, 25 Jun 2008 11:06:17 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jun 2008 10:05:11 -0500 Message-ID: <0489D0DE749FD2489EEB99455DEB6A7F082817FA@svr-fp-exch.dalair.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PHP-DEV] Overloading Thread-Index: AcjW0trqHIgWDW4RT3uR2Fesnc4IuQAAfIAg To: "Lukas Kahwe Smith" , "Marcus Boerger" Cc: Subject: RE: [PHP-DEV] Overloading From: MTinsley@dallasairmotive.com ("Tinsley, Mark") Thank you Lukas. Mark Tinsley Developer Dallas Airmotive (214) 353-6739 mtinsley@dallasairmotive.com =20 -----Original Message----- From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]=20 Sent: Wednesday, June 25, 2008 9:51 AM To: Marcus Boerger Cc: Tinsley, Mark; internals@lists.php.net Subject: Re: [PHP-DEV] Overloading On 20.06.2008, at 16:28, Marcus Boerger wrote: > Hello Mark, > > we discussed overloading a hell lot of times an dthe conclusionj =20 > always > and every single time has been NO. It would mean a large slowdown for > every single PHP application out there and it is not really that much > halpful. In fact it makes code less readable and maintainable so it > opposes the KISS (Keep It Simple Safe) approach of PHP. FYI, for future reference I at least added a link to the rfc page to =20 this thread: http://wiki.php.net/rfc#declined regards, Lukas Kahwe Smith mls@pooteeweet.org