Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127311
Precedence: bulk
MIME-Version: 1.0
Date: Wed, 07 May 2025 22:02:33 +0200
To: Niels Dossche <dossche.niels@gmail.com>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Initial discussion - more deprecation options
In-Reply-To: <5eebf119-aeff-4d1e-8f84-0e91f7c89bb4@gmail.com>
References: <CALaXqqT1s3Qyhi0FEfybbycjefwUSuojENaU1owfUV_nMHxAog@mail.gmail.com>
 <5eebf119-aeff-4d1e-8f84-0e91f7c89bb4@gmail.com>
Message-ID: <c3232274267ef2ca4d1833408e73c8c7@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-05-07 21:43, schrieb Niels Dossche:
> Definitely NAK on deprecating properties, which has the potential of 
> adding lots of overhead.

FWIW: Deprecating properties is already possibly by means of deprecating 
a property hook. I guess this is an acceptable workaround to not require 
a dedicated support + associated complexity.

see: https://3v4l.org/C6jRQ

     class Foo
     {
         public string $foo
         {
             #[\Deprecated]
             get {
                 return $this->foo;
             }

             #[\Deprecated]
             set {
                 $this->foo = $value;
             }
         }
     }

     $f = new Foo();
     $f->foo = 'dummy';
     var_dump($f->foo);

Best regards
Tim Düsterhus