Bug #79920 [Opn->Fbk]: Parse error doesn't emit line number in error message

From: Date: Sat, 01 Aug 2020 15:24:15 +0000
Subject: Bug #79920 [Opn->Fbk]: Parse error doesn't emit line number in error message
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-228359@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=79920&edit=1 ID: 79920 Updated by: cmb@php.net Reported by: info at joomlager dot de Summary: Parse error doesn't emit line number in error message -Status: Open +Status: Feedback Type: Bug -Package: *Compile Issues +Package: Scripting Engine problem Operating System: Windows10 PHP Version: 8.0.0alpha3 -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: Well, PHPUnit 8.5.8 is not (necessarily) compatible with PHP 8. Can you reproduce the issue directly (i.e. without PHPUnit)? Previous Comments: ------------------------------------------------------------------------ [2020-07-31 10:17:55] info at joomlager dot de Description: ------------ I'm running PHPUnit 8.5.8 on our codebase and tested it with PHP8. Unfortunately it seems to fail on the newly introduced reserved token "match" somewhere. However the error message is just ParseError: syntax error, unexpected token "match", expecting identifier or "static" or "namespace" or "\" without any file or line number given. I do get a stack trace, but the files and line numbers given in there, are nowhere near where the parse error seems to happen. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=79920&edit=1

« previous php.bugs (#228359) next »