Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120906
To: internals@lists.php.net
References: <CAFPFaMLBZixUFa=7=9Gxj60D=4QyfSpF9se-U+6CRoShzCrFrA@mail.gmail.com>
 <64DA7ACC.1050909@adviesenzo.nl>
 <FC25D227-5F08-4C00-BD64-961DB57C4423@php.net>
Message-ID: <64DAB72A.7000905@adviesenzo.nl>
Date: Tue, 15 Aug 2023 01:22:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <FC25D227-5F08-4C00-BD64-961DB57C4423@php.net>
Content-Type: multipart/alternative;
 boundary="------------090002030306050809000905"
Subject: Re: [PHP-DEV] Removing support for the disable_classes INI setting
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

--------------090002030306050809000905
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 15-8-2023 0:52, Derick Rethans wrote:
> On 14 August 2023 20:04:44 BST, Juliette Reinders Folmer <php-internals_nospam@adviesenzo.nl> wrote:
>
>> Declaring an ini directive in the php.ini
>> file which has been removed will instantly
>> cause a fatal error on starting PHP, so
>> I wonder what the impact will be
>> when a user switches PHP version
>> (which they often can choose to do
>> via a control panel).
> Are you sure about that? Setting ini entries that don't exist are simply ignored.
>
> For example this will generate no warning, and certainly not a fatal error:
>
> php -d elephpant.smells=no your-script.php
>
> cheers
> Derick
>

I though the same, then I ran some tests locally.... (before sending the 
mail) don't tell me I managed to test with the *one* ini setting which 
does cause a fatal ?

  php -d allow_call_time_pass_reference=true your-script.php

Smile,
Juliette

--------------090002030306050809000905--