Hi! I am rather more in favour of what you are proposing than the removal of static calls to FFI methods.
In my opinion, it would be possible to drop the deprecation if it is agreed in the RFC process. The static access to FFI methods is not yet a feature actually removed, and I think it may even be possible to remove the deprecation in a point release of 8.3. I am a little more worried about the way you communicate than the content of your proposal. For example, in my opinion, "stupid" is too strong a word for the tone of language typically found in this internals ML. If you have no intention of ridiculing the person who proposed deprecation or people who voted yes to the proposal, and the strong language was used just because of the language barrier, it would be probably better to make that clear. Perhaps no one cares about trivial wording. Personally I don't care. But if by any chance strong wording prevents constructive discussion, no one will be happy. -- Shinji Igarashi 2024年7月6日(土) 11:17 chopins xiao <chopins.x...@gmail.com>: > > My Submit RFC: > https://wiki.php.net/rfc/ffi-non-static-deprecated > > Since no one responded to the first announcement, I am not sure if anyone > agrees, so I will announce it again。 > > Since this RFC is the opposite of a PR, and the PR has already been merged > and is expected to be released in PHP 8.4, can the PR be revoked first? > Or do you all agree with the stupid PR?
