Re: my take on PHP 6, part 2

From: Date: Mon, 17 Feb 2014 21:02:38 +0000
Subject: Re: my take on PHP 6, part 2
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 


    - Native ctype support (no, not the current supported one. Look for its
    support in Python)
Not an engine feature. feel free to provide an extension API, eventually might be bundled. (and enabled by default / force) the ctype equivilent in php would be a more robust and accessible FFI http://pecl.php.net/package/ffi I think the goal here would be to expose lib's and be able to dynamically-ish (program via php) an interface to a library without having to write an extension. 
    - With better opcache and ctype, also add better dl(), completely
    removing the need to have so many extensions in core
Better dl is not trivial due to operating system restrictions. With major refactoring we might improve this a bit, but things which come to mind cause major breakage in APIs for quite little effect ... I thought a while about this in regards to composer etc.
I think the idea here is to be able to have per-project extension dependencies, as you said, with composer. This would be ideal in a way for the ecosystem to vet extensions before inclusion in core. But currently, unless you own the system, extensions are extremely inaccessible to gain any real momentum. -ralph

Thread (25 messages)

« previous php.internals (#72663) next »