Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63595 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87209 invoked from network); 21 Oct 2012 18:54:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2012 18:54:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=amaury.bouchard@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=amaury.bouchard@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender) X-PHP-List-Original-Sender: amaury.bouchard@gmail.com X-Host-Fingerprint: 209.85.161.170 mail-gg0-f170.google.com Received: from [209.85.161.170] ([209.85.161.170:52848] helo=mail-gg0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E8/16-22055-ED444805 for ; Sun, 21 Oct 2012 14:54:22 -0400 Received: by mail-gg0-f170.google.com with SMTP id q6so382670ggc.29 for ; Sun, 21 Oct 2012 11:54:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=pFXfBj8ijT02zqAtn2CAS1ZnlHokDpWme7qso/aYtyc=; b=jN2oAK/Aw2TTgGLSwSUZcCucKZWVmRjeVYMPsqg+i1CfbdZPOiNDJ8DfRVVH3Zb/Ed Uflf8zNFC98zuQysO07AwUjOnhRHSssuWbbzxEZLhLHZGfV/r5KoY1TLkZZVLvE2ruh4 rRc7DnNETlQnjWGgzzg9rh3Ak66FOFuyXcbGzhjoBja2Z1TivmSdwQ/L7LlgL9WQYPE7 2vowuV+bamrDzPDHy3T3jcdRq2dvarKsFbNua9Sv05xfdXSFtoLHbAOoL3YdPjMVGdrO iZcYtzIV5rYYWnWdchrw8gcAPND1DSEJj1IG19GKi1VuRtdNGUO1uXCAz7clRldiZJDQ zpcA== Received: by 10.236.76.42 with SMTP id a30mr6594600yhe.50.1350845658909; Sun, 21 Oct 2012 11:54:18 -0700 (PDT) MIME-Version: 1.0 Sender: amaury.bouchard@gmail.com Received: by 10.147.152.21 with HTTP; Sun, 21 Oct 2012 11:53:58 -0700 (PDT) In-Reply-To: References: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local> Date: Sun, 21 Oct 2012 20:53:58 +0200 X-Google-Sender-Auth: -CEH30qaKRzuX-AuBCgebeKpaeI Message-ID: To: Levi Morrison Cc: Nikita Popov , Clint Priest , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=20cf303b433ba54ca404cc9643b5 Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords From: amaury@amaury.net (Amaury Bouchard) --20cf303b433ba54ca404cc9643b5 Content-Type: text/plain; charset=ISO-8859-1 2012/10/21 Levi Morrison > I would like to point out that in my mind `const` and `read-only` are > not necessarily the same thing. Read-only means that from outside the > class it cannot be modified; the internal class can change it whenever > it wants. Const means that once the value is set it will NEVER change. > Big difference. > "read-only" means that it is only readable. Like const. If the internal class can change it, you are defining writing visibility (as private or protected). Yes, it is different. Visibility has far more meaning than just saying it's a constant value. In fact, "read-only" is a sub-case of usual visibility management. --20cf303b433ba54ca404cc9643b5--