Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125286
Date: Mon, 26 Aug 2024 14:49:56 -0400
To: Bilge <bilge@scriptfusion.com>
Cc: "=?utf-8?Q?internals=40lists.php.net?=" <internals@lists.php.net>
Message-ID: <8F591468-848C-413A-AD2C-47E003B56BEE@getmailspring.com>
In-Reply-To: <1c2cb0d4-ecf2-41c7-9f31-e90f1bee3805@scriptfusion.com>
References: <1c2cb0d4-ecf2-41c7-9f31-e90f1bee3805@scriptfusion.com>
Subject: Re: [PHP-DEV] [RFC] Default expression
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="66ccce54_643c9869_12a23"
From: john@coggeshall.org (John Coggeshall)

--66ccce54_643c9869_12a23
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



On Aug 26 2024, at 2:39 pm, Bilge <bilge@scriptfusion.com> wrote:
>
> I like this approach. I'm still not sure I'd want to pursue adding exclusions, but if we can identify something that's obviously bad and/or dangerous then we can consider that short list for exclusion. That is much more compelling than starting out by banning everything and arbitrarily whitelisting those things someone personally has a use for.
Perhaps the answer could be to only allow the use of default when the assigned default value is a scalar value -- no objects, arrays, enums, etc (and no mixed ).. It seems like a compromise that accomplishes a healthy portion of the stated use-cases while avoiding many of the foot-guns scenarios.
Coogle
(PS - I'm going to start signing off with my old-skool nickname around here, feel free to reference me using it to disambiguate since there are multiple Johns)


--66ccce54_643c9869_12a23
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><br><div class=3D=22gmail=5Fquote=5Fattribution=22>On Aug 26 2024, at=
 2:39 pm, Bilge &lt;bilge=40scriptfusion.com&gt; wrote:</div><blockquote>=
<br><div>I like this approach. I'm still not sure I'd want to pursue addi=
ng exclusions, but if we can identify something that's obviously bad and/=
or dangerous then we can consider that short list for exclusion. That is =
much more compelling than starting out by banning everything and arbitrar=
ily whitelisting those things someone personally has a use for.</div></bl=
ockquote><br><div>Perhaps the answer could be to only allow the use of <c=
ode>default</code>&nbsp; when the assigned default value is a scalar valu=
e -- no objects, arrays, enums, etc (and no <code>mixed</code>&nbsp;).. I=
t seems like a compromise that accomplishes a healthy portion of the stat=
ed use-cases while avoiding many of the foot-guns scenarios.</div><br><di=
v>Coogle</div><div>(PS - I'm going to start signing off with my old-skool=
 nickname around here, feel free to reference me using it to disambiguate=
 since there are multiple Johns)</div><br>
--66ccce54_643c9869_12a23--