php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #79180 Conflicts with inherited typed property types should be exceptions not errors
Submitted: 2020-01-27 22:50 UTC Modified: 2020-01-27 23:17 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: bugreports at gmail dot com Assigned:
Status: Open Package: Class/Object related
PHP Version: 7.4Git-2020-01-27 (Git) OS:
Private report: No CVE-ID: None
 [2020-01-27 22:50 UTC] bugreports at gmail dot com
Description:
------------
PHP Fatal error:  Type of test_typed_properties_extended::$int must be int (as in class test_typed_properties)

why are such errors not catchable as nearly anything else like parse errors in the recent history? not helpful when a testsuite designed to collect all errors and warnings and present them at the end silently stops while it would echo error_log normally as final action

try
{
 require $testfile;
}
catch(Throwable $exception)
{
 $this->trigger_error("custom/{$basename_testfile} - Exception - {$this->format_exception((string)$exception)}");
}


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2020-01-27 22:57 UTC] requinix@php.net
-Summary: not catchable +Summary: Conflicts with inherited typed property types should be exceptions not errors -Type: Bug +Type: Feature/Change Request -Package: Scripting Engine problem +Package: Class/Object related
 [2020-01-27 23:17 UTC] nikic@php.net
Inheritance errors are not catchable for technical reasons. I don't see this changing anytime soon.
 [2022-02-07 06:37 UTC] madampayal55 at gmail dot com
I am Madam Payal and I am Guwahati call girls for genuine live video calls. 
http://www.madampayal.com
https://www.payalrostogi.com
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Dec 21 12:01:31 2024 UTC