I don't disagree (sure, I campaigned to remove the "read-only" keyword). But "not writable" is still different from "private writing". Should we loose any of these meanings?
2012/10/21 Clint Priest <cpri...@zerocue.com> > I think that seems to be the consensus at this point, anyone disagree? > > > -----Original Message----- > > From: Levi Morrison [mailto:morrison.l...@gmail.com] > > Sent: Sunday, October 21, 2012 10:26 AM > > To: Amaury Bouchard > > Cc: Nikita Popov; Clint Priest; internals@lists.php.net > > Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords > > > > > If for some reason you need to enforce that nobody inherits it and > > > sets the property, then declaring a setter and issuing an error or > > > exception would suffice. > > > > I meant to say declaring a `private or final setter`. Noticed that > after I sent it. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
