Bug #80225 [Com]: broken namespace usage in eval code
| From: | remi@php.net | Date: | Mon, 12 Oct 2020 14:56:33 +0000 |
| Subject: | Bug #80225 [Com]: broken namespace usage in eval code | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-229584@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=80225&edit=1
ID: 80225
Comment by: remi@php.net
Reported by: remi@php.net
Summary: broken namespace usage in eval code
Status: Closed
Type: Bug
Package: Scripting Engine problem
Operating System: GNU/Linux
PHP Version: 8.0.0rc1
Assigned To: nikic
Block user comment: N
Private report: N
New Comment:
Well, NOOP before declare was not allowed in previous versions, so can also stay like now.
Previous Comments:
------------------------------------------------------------------------
[2020-10-12 14:51:57] remi@php.net
> It makes me wonder if we shouldn't also lift this restriction for declare(strict_types)...
>
I think it make sense
------------------------------------------------------------------------
[2020-10-12 14:42:12] nikic@php.net
It makes me wonder if we shouldn't also lift this restriction for declare(strict_types)... That
is allow
<?php ; declare(strict_types=1); or ?><?php
declare(strict_types=1); in eval.
------------------------------------------------------------------------
[2020-10-12 14:40:34] remi@php.net
Thanks for the quick fix.
(for memory was affecting mockery/mockery).
------------------------------------------------------------------------
[2020-10-12 14:35: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=f9b7609d17694c5b5d5bba6321b27944220566be
Log: Fixed bug #80225
------------------------------------------------------------------------
[2020-10-12 14:30:53] nikic@php.net
Basically same as https://3v4l.org/bBCrm. No idea if
that's "right", but I guess we can just match the previous behavior.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=80225
--
Edit this bug report at https://bugs.php.net/bug.php?id=80225&edit=1