php-src/Zend/tests/offset_assign.phpt

--TEST--
Crash on $x['2x']['y'] += 1 when $x is string
--FILE--
<?php
$x = "a";
$x['2x']['y'] += 1;

echo "Done\n";
?>
--EXPECTF--
Warning: Illegal string offset "2x" in %s on line %d

Fatal error: Uncaught Error: Cannot use string offset as an array in %soffset_assign.php:%d
Stack trace:
#0 {main}
  thrown in %soffset_assign.php on line %d
fix crash on $x['x']['y'] += 1, patch by Brian Shire 2007-03-08 20:59:31 +00:00			`--TEST--`
Implement 'Saner Numeric Strings' RFC: RFC: https://wiki.php.net/rfc/saner-numeric-strings This removes the -1 allow_error mode from is_numeric_string functions and replaces it by a trailing boolean out argument to preserve BC in a couple of places. Most of the changes can be resumed to "numeric" strings which emitted a E_NOTICE now emit a E_WARNING and "numeric" strings which emitted a E_WARNING now throw a TypeError. This mostly affects: - String offsets - Arithmetic operations - Bitwise operations Closes GH-5762 2020-07-29 01:51:09 +00:00			`Crash on $x['2x']['y'] += 1 when $x is string`
fix crash on $x['x']['y'] += 1, patch by Brian Shire 2007-03-08 20:59:31 +00:00			`--FILE--`
			`<?php`
			`$x = "a";`
Implement 'Saner Numeric Strings' RFC: RFC: https://wiki.php.net/rfc/saner-numeric-strings This removes the -1 allow_error mode from is_numeric_string functions and replaces it by a trailing boolean out argument to preserve BC in a couple of places. Most of the changes can be resumed to "numeric" strings which emitted a E_NOTICE now emit a E_WARNING and "numeric" strings which emitted a E_WARNING now throw a TypeError. This mostly affects: - String offsets - Arithmetic operations - Bitwise operations Closes GH-5762 2020-07-29 01:51:09 +00:00			`$x['2x']['y'] += 1;`
fix crash on $x['x']['y'] += 1, patch by Brian Shire 2007-03-08 20:59:31 +00:00
			`echo "Done\n";`
			`?>`
Trim trailing whitespace in tests 2018-09-16 17:16:42 +00:00			`--EXPECTF--`
Implement 'Saner Numeric Strings' RFC: RFC: https://wiki.php.net/rfc/saner-numeric-strings This removes the -1 allow_error mode from is_numeric_string functions and replaces it by a trailing boolean out argument to preserve BC in a couple of places. Most of the changes can be resumed to "numeric" strings which emitted a E_NOTICE now emit a E_WARNING and "numeric" strings which emitted a E_WARNING now throw a TypeError. This mostly affects: - String offsets - Arithmetic operations - Bitwise operations Closes GH-5762 2020-07-29 01:51:09 +00:00			`Warning: Illegal string offset "2x" in %s on line %d`
implement the solution for isset/string offsets, fix bug #60362 2011-12-19 02:05:03 +00:00
Update exception names in tests after formatting changes. 2015-05-17 22:31:43 +00:00			`Fatal error: Uncaught Error: Cannot use string offset as an array in %soffset_assign.php:%d`
Display EngineExceptions like ordinary exceptions TypeException stays as-is for now because it uses messages that are incompatible with the way exception messages are displayed. closure_038.phpt and a few others now show that we're generating too many exceptions for compound operations on undefined properties -- this needs to be fixed in a followup. 2015-05-15 19:04:07 +00:00			`Stack trace:`
			`#0 {main}`
			`thrown in %soffset_assign.php on line %d`