Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119338
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-1187-g678636ba0d-fm-20230113.001-g678636ba
Mime-Version: 1.0
Message-ID: <d34314aa-8a99-4268-8ef5-beaa19867429@app.fastmail.com>
In-Reply-To: 
 <CAFDBR4ZmckzW52tcJSGM=CyGNEXW=gLSY0qW1zW12SW8HKXGag@mail.gmail.com>
References: 
 <CAFDBR4ZmckzW52tcJSGM=CyGNEXW=gLSY0qW1zW12SW8HKXGag@mail.gmail.com>
Date: Wed, 18 Jan 2023 16:29:23 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] Measuring Proposal Reaction
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Jan 17, 2023, at 1:25 PM, Jesse G. Donat wrote:
> I'm looking to measure reaction to a proposal.
>
> My proposal is to have the STDOUT and STDERR global constants always
> defined rather than just when running via CLI.
>
> The variability of their existence is a common cause of confusion for
> younger inexperienced devs, and even something that slips the mind of more
> experienced developers.
>
> My team actually internally has a sniff forbidding STDOUT and STDERR due to
> their unreliability in favor of fopenening php://stdout / php://stdout
>
> I think removing the environment variability between CLI and Web
> outweighs the potential problems of people writing to these in the wrong
> contexts, especially given that you can already fopen and fwrite to
> standard out and standard error from a web session.
>
> This is only my second RFC I've purprosed so I'm pretty new to the process.
> Let me know what you think and what I can do to help
>
> Thanks,
>
> Jesse G. Donat

Does anyone know why those constants are left out?  Given that the functionality can still be used, as noted...

--Larry Garfield