Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113963
To: internals@lists.php.net
References: <CAES=RMtF9FbRgRrigbm8mew38z8Yba9aZobibJCuquOt8a_uWA@mail.gmail.com>
Cc: Jesse Rushlow <jr@rushlow.dev>
Message-ID: <0c5e70d7-5b11-5251-4ec9-608db63105c9@gmail.com>
Date: Mon, 5 Apr 2021 20:30:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <CAES=RMtF9FbRgRrigbm8mew38z8Yba9aZobibJCuquOt8a_uWA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Path forward for class_exists with different targeted
 PHP version implementations
From: rowan.collins@gmail.com (Rowan Tommins)

On 05/04/2021 18:14, Jesse Rushlow wrote:
> I was attempting to use class_exists(UsesPropertyPromotion::class) to
> determine if an attribute implementation existed in order to generate a PHP
> 8 appropriate class - else fall back to generating a PHP 7 appropriate
> class. For context, this check was being written for Symfony's MakerBundle
> which generates classes for Symfony projects.


Hi Jesse,

Can you explain the use case in a bit more detail, perhaps giving some 
example code you were hoping to write with class_exists()?

I suspect there are other ways to achieve what you were trying to do, 
but don't want to confuse things if I've misunderstood the requirements.

Regards,

-- 
Rowan Tommins
[IMSoP]