Bug #80334 [Com]: assert() vs named parameters - confusing error

Edit report at https://bugs.php.net/bug.php?id=80334&edit=1 ID: 80334 Comment by: bugs dot php dot net_nospam at adviesenzo dot nl Reported by: bugs dot php dot net_nospam at adviesenzo dot nl Summary: assert() vs named parameters - confusing error Status: Closed Type: Bug Package: *General Issues Operating System: N/A PHP Version: 8.0.0RC3 Block user comment: N Private report: N New Comment: Thanks @nikic! Previous Comments: ------------------------------------------------------------------------ [2020-11-09 09:19:55] nikic@php.net Automatic comment on behalf of nikita.ppv@gmail.com Revision: http://git.php.net/?p=php-src.git;a=commit;h=6fb3d92525d28f0b617a53d05a6be74a3ef37fa5 Log: Fixed bug #80334 ------------------------------------------------------------------------ [2020-11-09 09:02:49] nikic@php.net The problem is that we're appending the generated message to the arguments, which doesn't work for named args. ------------------------------------------------------------------------ [2020-11-07 22:30:45] bugs dot php dot net_nospam at adviesenzo dot nl Description: ------------ The "Cannot use positional argument after named argument" exception is sometimes thrown in situations where named parameters isn't supported. Test script: --------------- <?php $null = null; // https://3v4l.org/qgfV2 assert(assertion: is_null($null)); // https://3v4l.org/q8Oqq $a = is_null($null); assert(assertion: $a); Expected result: ---------------- Either named parameters being supported (= no error). Or named parameters not being supported and the code resulting in a parse error. NOT an error referring to named arguments, while the language construct doesn't seem to support it. Actual result: -------------- Fatal error: Cannot use positional argument after named argument in /in/qgfV2 on line 3 ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=80334&edit=1