On 3 November 2023 19:46:25 GMT, dan...@daniil.it wrote:
>Nothing will change in that sense, the only difference is the addition of
>compile-time autoloading and type checking.
>
>No preloading (in the sense of no opcache configuration needed), nothing
>special.
OK; just to explain the confusio
On Fri, Nov 3, 2023 at 6:49 PM wrote: added in php 8.3,
that's why I couldn't find it in the docs :)
>
> Respectfully, I will still be editing the deprecations RFC anyway to see
> if the voting passes.
>
>
Hmm, didn't you say this previously:
> The main reason I would like to see this deprecated
Hi,
> There are still a lot of people who use a cheap shared host, edit a file
> directly on the live environment, and expect it to just work without needing
> any kind of rebuild or restart step.
Nothing will change in that sense, the only difference is the addition of
compile-time autoloadi
On 3 November 2023 16:05:52 GMT, dan...@daniil.it wrote:
> (of course this would be somewhat of a breaking change, PHP 9-worthy).
I think this is rather an understatement. This would be a HUGE change for many
users of the language, and expect a lot of pushback for any such proposal.
There are s
Hi,
> It is exposed:
> https://github.com/php/php-src/blob/66e2aa725564c2221ace7a26628afe3957f28237/ext/posix/posix.c#L1232-L1241
>
Welp completely missed that, my bad, it was added in php 8.3, that's why I
couldn't find it in the docs :)
Respectfully, I will still be editing the deprecations R
On Thu, Nov 2, 2023 at 11:11 PM wrote:
> 1) Not all POSIX functions are currently exposed by the POSIX extension,
> sysconf being one of the missing ones (with IMO no good reason to add it)
>
It is exposed:
https://github.com/php/php-src/blob/66e2aa725564c2221ace7a26628afe3957f28237/ext/posix/po
Hi
On 11/3/23 00:14, dan...@daniil.it wrote:
This deprecation appears to be sufficiently simple that it can likely be
included in the bulk deprecation RFC for PHP 8.4:
https://wiki.php.net/rfc/deprecations_php_8_4
That would be super nice, who should I ping before editing the page?
I'd sa
Hi,
> Doesn't that just take us back to the "generic types are only optionally
> checked" scenario you were trying to avoid?
Of course, my idea would also require bundling and enabling opcache by default
with PHP and actually requiring the preloading+compilation step in order to run
any code,
On 3 November 2023 13:15:59 GMT, Daniil Gentili wrote:
>Well, I was actually thinking of enabling these compile-time checks only if
>preloading is enabled, to ensure the closed-world guarantee.
Doesn't that just take us back to the "generic types are only optionally
checked" scenario you were t
Hi Ilija,
The optimizer, including type inference, is limited to the scope of
the current file (along with internal functions/classes). [...]
Preloading is the exception, where all preloaded files can assume not
to be changed after PHP has booted.
Well, I was actually thinking of enabling thes
Hi,
I don't think this inclusion is a problem, but I also don't see any real
benefits.
Some parts of the syntax should be verbose to make it easier to read and
understand, especially for those who are just arriving.
Soon, people will want to be writing `pub` instead of `public`, or `priv`
instea
Hi Daniil
On Fri, Nov 3, 2023 at 12:00 AM wrote:
> The much better approach, one that I intend to maybe give a shot at this
> Christmas, is to add static analysis functionality to PHP itself (i.e. turn
> it into a truly statically typed language).
> I have a hunch it may be easy enough to do by
12 matches
Mail list logo
