Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124142
Precedence: bulk
MIME-Version: 1.0
References: <CAEUnE0fGZ3jFiBG=GyvnhBzH5a0iO4=n75PM=3+6zLAMrumEvA@mail.gmail.com>
 <CADK1yX+E9mvaM_CHJ8tmEx=O70hf8xasbvngh4wvNM8ce8KKGQ@mail.gmail.com>
 <B5DC69B8-E044-47FB-B81C-307E2C19CB66@newclarity.net> <1917CF7C-26D8-4DBE-B05C-5AA650AC6C9F@rwec.co.uk>
 <551cd5b0-1c00-4818-a9ca-97f6b7e8c3dc@app.fastmail.com> <CAEUnE0fNxSHN4QGfm6ETMVdE5Mcm1AEebmWs7i9xDNgcWnvQvw@mail.gmail.com>
 <39B496F8-062E-4848-9B3B-529BE8D3415A@newclarity.net> <CAEUnE0fOfU1tJNKXuBqbSm8jsp7gqe_JY-SiipdUKNztcx0Rog@mail.gmail.com>
 <856F4F70-DC81-4098-82DD-5F6D47CDF3F0@newclarity.net> <CAEUnE0c0fW9xnQOtLgj1zTpvdfixSHuLeLA7HOqDTkpr4hJ84g@mail.gmail.com>
 <CAEUnE0dSUY2VKji_o-AgQ-YZMf7viwCZh1sa8ScHdS7ihUgfUQ@mail.gmail.com> <217db044-e356-4e18-ba68-c18dce6381a5@app.fastmail.com>
In-Reply-To: <217db044-e356-4e18-ba68-c18dce6381a5@app.fastmail.com>
Date: Mon, 1 Jul 2024 22:37:49 +0900
Message-ID: <CAOyH9yRptLsZ_zuW1aEkbmV+z+8qz8p0ARqMpvg3FCb4VaEN=g@mail.gmail.com>
Subject: Re: [PHP-DEV] Iteration III: Packages (was Re: [PHP-DEV] [Initial
 Feedback] PHP User Modules - An Adaptation of ES6 from JavaScript)
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: alex.pravdin@interi.co (Alexander Pravdin)

Sorry for getting into this hot topic. Just wanted to add my two cents.

> Really, the only targets we should be looking at, IMO, are:
>
> 1. Package-level visibility.
> 2. Giving the compiler/optimizer/JIT a larger "scope" of code to compile/optimize at once, so it can do smarter things.
>
> I think everything else is a distraction.

As a userland developer, I like one of the author's intentions - to
allow writing modern PHP code without poor legacy, without opening
tags, which will also enable the compiler to apply more magick and
more optimizations. I could see it as a new file extension, for
example, "phpx" and release it in PHP10. This will not drop BC and at
the same time, users will have the opportunity to explicitly tell the
compiler that they want to use the new format. The inclusion of
old-style files will still be allowed. In the far future, we may
feature-freeze old-style files and gradually migrate to the new ones.
I personally support the movement from the current "plain-text
template-first" language to a "coding-first" language, where files
contain code by default. We already support multiline raw strings in
PHP code so the usage in templates should not suffer. Or it can even
be simplified by introducing a better way to craft templates in the
new "coding-first" format of PHP files.

I also support the idea of having packages with private members,
autoloading constants and functions without using classes.

--
Alexander.