5 Commits

Author	SHA1	Message	Date
George Peter Banyard	99fa740acb	Use common function for TypeError on illegal offset access (#10544) ... This merges all usages of emitting an offset TypeError into a new ZEND_API function zend_illegal_container_offset(const zend_string* container, const zval *offset, int type); Where the container should represent the type on which the access is attempted (e.g. string, array) The offset zval that is used, where the error message will display its type The type of access, which should be a BP_VAR_* constant, to get special message for isset/empty/unset	2023-06-06 11:28:19 +01:00
Marcos Marcolin	641fe23e3a	Improve illegal offset error messages (#10504) ... Co-authored-by: Marcos Marcolin <marcos@ixcsoft.com.br>	2023-02-08 12:11:41 +00:00
Ayesh Karunaratne	b8e380ab09	Update deprecation message for incompatible float to int conversion ... Updates the deprecation message for implicit incompatible float to int conversion from: ``` Implicit conversion from non-compatible float %.*H to int in %s on line %d ``` to ``` Implicit conversion from float %.*H to int loses precision in %s on line %d ``` Related: #6661	2021-06-07 14:36:11 +02:00
George Peter Banyard	b6958bb847	Implement "Deprecate implicit non-integer-compatible float to int conversions" RFC. (#6661) ... RFC: https://wiki.php.net/rfc/implicit-float-int-deprecate Co-authored-by: Nikita Popov <nikita.ppv@gmail.com>	2021-05-31 15:48:45 +01:00
Máté Kocsis	14bdb0cfc7	Fix consistency issues with array accesses warnings/exceptions ... * Change a number of "resource used as offset" notices to warnings, which were previously missed. * Throw the "resource used as offset" warning for isset() as well. * Make array_key_exists() behavior with regard to different key types consistent with isset() and normal array accesses. All key types now use the usual coercions and array/object keys throw TypeError. Closes GH-4887.	2019-11-06 12:56:47 +01:00