imsop-suggestion

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/02/27 20:46		current
Line 263:		Line 263:
	For the vast majority of properties this causes no issue, as reading or writing to properties by reference is extremely rare. However, there are some edge cases where references to properties are necessary. Arguably, the lack of support for references would technically make adding hooks to a property a nominal BC break for that class, but property references are so rare that we consider it acceptable, especially with the addition below.		For the vast majority of properties this causes no issue, as reading or writing to properties by reference is extremely rare. However, there are some edge cases where references to properties are necessary. Arguably, the lack of support for references would technically make adding hooks to a property a nominal BC break for that class, but property references are so rare that we consider it acceptable, especially with the addition below.

-	In cases where the user considers it acceptable to by-pass the ''set'' hook using indirect modification, the ''get'' hook can be replaced by an ''&get'' hook. This works identically to a normal ''get'' hook, but the body must meet the normal requirements for returning by reference. Subsequent writes to that reference will not trigger the ''set'' hook.	+	In cases where the user considers it acceptable to bypass the ''set'' hook using indirect modification, the ''get'' hook can be replaced by an ''&get'' hook. This works identically to a normal ''get'' hook, but the body must meet the normal requirements for returning by reference. Subsequent writes to that reference will not trigger the ''set'' hook.

	That means the following is allowed:		That means the following is allowed:

PHP Wiki - rfc:property-hooks

imsop-suggestion