Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110087
MIME-Version: 1.0
References: <CAF+90c8tW27-rhrk8pLieMsEWa4WHEBciPX1zThME68zf6s2QQ@mail.gmail.com>
 <1C09C0A9-1DA4-4753-8E5A-A739D52DA0B3@newclarity.net>
In-Reply-To: <1C09C0A9-1DA4-4753-8E5A-A739D52DA0B3@newclarity.net>
Date: Fri, 8 May 2020 14:44:15 +0100
Message-ID: <CA+kxMuQoqaob8m9D8dO2OvZ8PFRY8nTuS4E-ok=F3Hy4-sJD8g@mail.gmail.com>
To: Mike Schinkel <mike@newclarity.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Parameter Blocks (vs. Constructor Property
 Promotion and Named Parameters)
From: Danack@basereality.com (Dan Ackroyd)

On Wed, 6 May 2020 at 20:49, Mike Schinkel <mike@newclarity.net> wrote:
>
> I am rather concerned about

Mike,

It's nice that you want to contribute to PHP. But trying to brainstorm
ideas over email is not productive.

Spending your time helping get the manual more up-to-date would be far
more beneficial than throwing out "Hey why don't you try this"
comments.

> a standard library of PHP-written functionality bundled in a PHAR file that would be included with future implementations of PHP and automatically included by PHP.

Anyone who has worked with Java or Go would know that having core
functionality separate from the executable would bring in a whole new
set of error conditions related to classpath or gopath. And
additionally version mismatch problems between the library found, and
the language executable being invoked.

Additionally, while both strings and arrays in PHP work, how they are
implemented leaves something to be desired. For strings, it's the
behaviour around character sets/unicode. For arrays, it's a 'having a
single data structure for all possible needs' problem.

Spending time on a 'standard library' before there have been
improvements to strings and/or arrays is unlikely to produce anything
of great value.

As I said, if you have energy that can be used to make PHP better, I
think helping with the manual would be useful
https://github.com/php/doc-en Or if you can, getting up to speed with
C to work on bugs would also be good https://bugs.php.net/ But just
throwing out ideas is not a productive use of your time and distracts
people from more useful conversations.

cheers
Dan
Ack