Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36551 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86809 invoked from network); 26 Mar 2008 17:05:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Mar 2008 17:05:19 -0000 Authentication-Results: pb1.pair.com header.from=indeyets@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=indeyets@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.142.187 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: indeyets@gmail.com X-Host-Fingerprint: 209.85.142.187 ti-out-0910.google.com Received: from [209.85.142.187] ([209.85.142.187:4653] helo=ti-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/FC-47041-D428AE74 for ; Wed, 26 Mar 2008 12:05:18 -0500 Received: by ti-out-0910.google.com with SMTP id a21so1349484tia.17 for ; Wed, 26 Mar 2008 10:05:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ONWFppu955ohafdYtfj3liOCadNXPPWSOmUMxUDs2d8=; b=M7SG5XT7+INXw8d34ytuP5yaT4Ipx0wLWzlltObhM+0BB0vEs+R4aqoE1QYVZYAYldBkysQ9WOSd6umC5/q3Nuow7Lt8PjB+R3tlAgazCsZ5JkM5Cg6e8pkYNfKP5neEImdaJHkqd2gWWVOStAcb9gtqUFb/VhBxOsz1UN+BObU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oM+M4eIu98as1/ums95dssoJ3JBaKsYBDxR4+fMlHfpAKFUxh2DCF9zT0k0xhljMGHoNFLFBIGyMhNN8MrA1vFfsc2S6f5MuX1jYYbZNDa0WyMyWgZOvdMGrXm5/9U1KN37IZuaWYbbdZc0nJqmahSwHBDqAW7gu9y+E0LaatKc= Received: by 10.150.204.19 with SMTP id b19mr166696ybg.63.1206551112291; Wed, 26 Mar 2008 10:05:12 -0700 (PDT) Received: by 10.150.57.12 with HTTP; Wed, 26 Mar 2008 10:05:12 -0700 (PDT) Message-ID: Date: Wed, 26 Mar 2008 20:05:12 +0300 To: RQuadling@googlemail.com Cc: "Felipe Pena" , "Lars Strojny" , "Robin Fernandes" , internals In-Reply-To: <10845a340803260956g6166feaboc04e55c88a9a1a8c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5a8807d10802050343r43742844we89366ec47b57f4b@mail.gmail.com> <46ccd1ab0803241816k413c7605p2c3fb9139afd8536@mail.gmail.com> <5a8807d10803250404o6fd33662wbbf3ff14d296cb2a@mail.gmail.com> <1206444907.11368.4.camel@localhost> <1206445347.5400.1.camel@felipe> <10845a340803260945u7a49d991uac5d39be13cca988@mail.gmail.com> <10845a340803260956g6166feaboc04e55c88a9a1a8c@mail.gmail.com> Subject: Re: [PHP-DEV] Inconsistencies when accessing protected members From: indeyets@gmail.com ("Alexey Zakhlestin") On 3/26/08, Richard Quadling wrote: > It just doesn't seem right to be able to call a private or protected > method of another instance. Sort of isn't private any more. > And as for being able to call a protected method of a completely > different class, just because it shares the same ancestry. That seems > REALLY wrong. it is needed for operations on several instances of the same class-hierarchy. "private" means, that you are the author of the class and you know what you are doing with instances of this class, but you do not want to export that inner-functionality. use case for "protected" is similiar, but relates to cases when you have hierarchy of classes, which still have some common functionality, which might be usable for multi-instance operations -- Alexey Zakhlestin http://blog.milkfarmsoft.com/