rfc:internal_constructor_behaviour
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| rfc:internal_constructor_behaviour [2015/03/15 18:07] – Added pr for clarity. danack | rfc:internal_constructor_behaviour [2015/04/01 09:59] – nikic | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| * Date: 2015-03-01 | * Date: 2015-03-01 | ||
| * Author: Dan Ackroyd, Danack@php.net | * Author: Dan Ackroyd, Danack@php.net | ||
| - | * Status: | + | * Status: |
| * First Published at: https:// | * First Published at: https:// | ||
| Line 215: | Line 215: | ||
| Should the standard paradigm for constructors for internal objects be to return a usable instance of a class on success, and throw an exception if they encounter an error, and should the code for the classes listed below be modified to follow this standard? | Should the standard paradigm for constructors for internal objects be to return a usable instance of a class on success, and throw an exception if they encounter an error, and should the code for the classes listed below be modified to follow this standard? | ||
| - | <doodle title=" | + | <doodle title=" |
| * Yes | * Yes | ||
| * No | * No | ||
rfc/internal_constructor_behaviour.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1