Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129644
Precedence: list
MIME-Version: 1.0
Date: Wed, 17 Dec 2025 21:07:32 +0100
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] isReadable/isWriteable property reflection
In-Reply-To: <bba7305f-de74-4913-88ec-2638ed25e52a@app.fastmail.com>
References: <e906b61e-b951-4eb4-aa0f-700e76dae6a9@app.fastmail.com>
 <09b0365c-9708-4c38-8004-5b1ca693ad8c@app.fastmail.com>
 <dbf4a553b5de5188d4bb33befe194f8c@bastelstu.be>
 <bba7305f-de74-4913-88ec-2638ed25e52a@app.fastmail.com>
Message-ID: <3dcb2def0d4d68187630401d1be8306a@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-12-17 20:48, schrieb Larry Garfield:
> Oh, and one other note: It turns out that in English, both "writeable" 
> and "writable" are nominally valid.  The latter seems more common (and 
> my spellchecker only recognizing the latter), so we've standardized on 
> the non-E version throughout the RFC.  (The code already was.)

As a non-native speaker, I confirm that “writable” without the “e” is 
what looks more familiar to me. It's also consistent with 
https://www.php.net/manual/en/function.is-writable.php (although that 
one has an alias https://www.php.net/manual/en/function.is-writeable.php 
- but since the one with the “e” is the alias, it is the less preferable 
variant).

Best regards
Tim Düsterhus