php-src/Zend/tests/gh8821.phpt

--TEST--
GH-8821: Fix reported line number of constant expression
--FILE--
<?php

enum Alpha {
    case Foo;
}

class Bravo {
    public const C = [Alpha::Foo => 3];
}

new Bravo();

?>
--EXPECTF--
Fatal error: Uncaught TypeError: Cannot access offset of type Alpha on array in %sgh8821.php:8
Stack trace:
#0 %sgh8821.php(11): [constant expression]()
#1 {main}
  thrown in %sgh8821.php on line 8
Fix lineno for all constant expressions Fixes GH-8821 Closes GH-8855 2022-08-04 12:12:45 +00:00			`--TEST--`
			`GH-8821: Fix reported line number of constant expression`
			`--FILE--`
			`<?php`

			`enum Alpha {`
			`case Foo;`
			`}`

			`class Bravo {`
			`public const C = [Alpha::Foo => 3];`
			`}`

			`new Bravo();`

			`?>`
			`--EXPECTF--`
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 10:28:19 +00:00			`Fatal error: Uncaught TypeError: Cannot access offset of type Alpha on array in %sgh8821.php:8`
Fix lineno for all constant expressions Fixes GH-8821 Closes GH-8855 2022-08-04 12:12:45 +00:00			`Stack trace:`
			`#0 %sgh8821.php(11): [constant expression]()`
			`#1 {main}`
			`thrown in %sgh8821.php on line 8`