Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91260 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90085 invoked from network); 17 Feb 2016 20:22:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2016 20:22:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.25.163 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.25.163 mx207.easyname.com Received: from [212.232.25.163] ([212.232.25.163:33291] helo=mx207.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F0/BE-17120-686D4C65 for ; Wed, 17 Feb 2016 15:22:31 -0500 Received: from cable-81-173-133-29.netcologne.de ([81.173.133.29] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aW8cF-00011H-4s for internals@lists.php.net; Wed, 17 Feb 2016 20:22:27 +0000 Reply-To: internals@lists.php.net References: <56C4B92E.9020306@fleshgrinder.com> To: internals@lists.php.net Message-ID: <56C4D67B.8040501@fleshgrinder.com> Date: Wed, 17 Feb 2016 21:22:19 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Traits with interfaces From: php@fleshgrinder.com (Fleshgrinder) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2/17/2016 9:01 PM, Kevin Gessner wrote: > > I'm not clear on the motivation for this principle. Is there > anything I could read up about explicit vs implicit in PHP design? > This is not so much about implicit vs. explicit PHP design for me. This is about inheriting something from a piece of "reusable dead code" (that is how I use to explain traits to youngsters). On 2/17/2016 9:01 PM, Kevin Gessner wrote: > > What cases are you thinking of here? I'm trying to come up with an > example where a class that wouldn't want an interface provided by a > trait it uses. > In any case in which you want to provide the same functionality as the trait provides but to not want to be of the same kind. On 2/17/2016 9:01 PM, Kevin Gessner wrote: > > I don't use a PHPDoc-aware IDE (I'm old fashioned), so I'd want any > change to be part of the language itself, where enforcement is > guaranteed. > That is unfortunate for you because you are missing out on many great features and that was even the case in the 1990s. However, I am not here to convince you of using an IDE. - -- Richard "Fleshgrinder" Fussenegger -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWxNZ7AAoJEOKkKcqFPVVrNh0P/2126wunMnqX1g698s3T1g2R olOzE3+tRLN8shmwl3/Gk2d8OoW4vsx5D0et/w2T2X0rIIBm2Fq7kRfQU5kmVL0x zTZkYL5oDxlasGNjlFqhJhPxILbrzrrSRK15DsGHOzau+hCdlXjK+Cs+UuXXzw4h Wk4Mbak16sWX4nWVdotB7otHrXNQCVAwyNuEfTIWEWVKBGzAzr8iMgmiaepgtUoT KclQOHdOHC1J2+16MiEK+P1wQZf/SMh2SecxFLBm/xRNerHXBYPM3yD9DDmDg+B7 K3BhRjI8fa45Xo7lQFxF9BI30IdupaJAYguPJeL7/w+NggiY0iq+5m/smrDEjrTz 01GmjN/2GTlN6xOTHXbnc+FdL7RTbGupmBBNXMJrjyxlFkjRFnDB0LxU3KsZj8MB RohVPmsZEqhlmGTXHSrf46Ps1AwPafheJDkXz4HASye+54umg0TIxPS3lzra+KIt 0a7O53t4NYvP1/Q1pwIg8iM+atrHmb5D55mHtzB4Z/zz/d0cIw6gO/arJAIgBO+S 10VlFnK1rPKVlUj0lk2kPEzMTmBQF6pYbjnnJoLuCID7UsYjABxYval6yT1yblSu zKcU0UXtlR6rJA9fN3P7VHWTn9U5nSFG8uRrN5LC+zJka+k5UenvYDTUCcbE+yfM Lwd7W7eM1zuBKIjYDtTL =+QfU -----END PGP SIGNATURE-----