Re: [RFC] Asymmetric Visibility, with readonly

Hi Larry, Regarding the syntax, up until now PHP has only supported the letters a-z and underscore in keywords. I realise this is an aesthetic thing, but "private(set)" looks like a function to me, and not a keyword. I saw the previous poll, and it didn't include options for either protected_set/private_set or protectedset/privateset. Was there a technical reason for excluding them as an option? On Sun, 13 Nov 2022 at 20:09, Larry Garfield <larry@garfieldtech.com> wrote: > > That creates an odd situation where readonly and asymmetric visibility > may only be combined "sometimes."... > > 2. Disallow readonly and asymmetric visibility being combined, because > readonly already has a hard-coded implied asymmetric visibility. This is getting quite complicated. I think unless someone makes a strong case for allowing the combination of the two, disallowing them being combined is probably the best choice. cheers Dan Ack