rfc:disallow-multiple-constructor-calls
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| rfc:disallow-multiple-constructor-calls [2017/01/17 20:39] – fleshgrinder | rfc:disallow-multiple-constructor-calls [2025/04/03 13:08] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== PHP RFC: Disallow Multiple Constructor Calls ====== | ====== PHP RFC: Disallow Multiple Constructor Calls ====== | ||
| - | * Version: 0.1 | + | * Version: 0.2 |
| * Date: 2017-01-17 | * Date: 2017-01-17 | ||
| * Author: Richard Fussenegger < | * Author: Richard Fussenegger < | ||
| - | * Status: | + | * Status: |
| * First Published at: https:// | * First Published at: https:// | ||
| Line 99: | Line 99: | ||
| Leaving the problem to the developers themselves. It is possible for developers to protect their objects against such unintended usage by asserting that all properties are null but this is unnecessary boilerplate code in a language that is already very verbose. | Leaving the problem to the developers themselves. It is possible for developers to protect their objects against such unintended usage by asserting that all properties are null but this is unnecessary boilerplate code in a language that is already very verbose. | ||
| - | We propose that multiple calls to the constructor of an object should result in an error instead of breaking encapsulation. This means in effect that the only idiomatic way to create a new instance is via the new keyword. Child classes are only permitted to call their parent constructor once and further calls are going to result in an error too. | + | We propose that multiple calls to the constructor of an object should result in an error instead of breaking encapsulation. This means in effect that the only idiomatic way to create a new instance is via the '' |
| - | This means in effect that the code examples posted earlier would result in errors, however, another code example that posted on internals as a legitimate use case for calling the constructor method directly would continue to work as is: | + | This means in effect that the code examples posted earlier would result in errors, however, another code example that was posted on internals as a legitimate use case for calling the constructor method directly would continue to work as is: |
| <code php> | <code php> | ||
| Line 150: | Line 150: | ||
| * Java does not support multiple calls (compiler error). | * Java does not support multiple calls (compiler error). | ||
| * JavaScript, Python, and Ruby allow multiple calls. | * JavaScript, Python, and Ruby allow multiple calls. | ||
| + | |||
| + | ==== Upgrade Paths ==== | ||
| + | We propose to include this change either in the next feature release or the next major. The decision is up to the voters. However, we propose that an error with severity '' | ||
| ===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
rfc/disallow-multiple-constructor-calls.1484685581.txt.gz · Last modified: 2025/04/03 13:08 (external edit)