On 19.07.2013, at 21:29, Igor Wiedler wrote:
> Hello internals,
>
> I posted the initial idea for a use_function RFC a few months back. I would
> like to make the proposal official now, and open it for discussion.
>
> I also did some work on a patch that probably still has some issues. Review
Hi Lars,
I don't really like the idea of such ghost features that don't actually do
anything. It sounds like it would just introduce wrong mappings. And since
those other constructs *do* share a namespace it technically wouldn't make
sense to make a distinction between them.
Any other thoughts
On Sun, Jul 21, 2013 at 6:14 PM, Jakub Zelenka wrote:
> On Tue, Jul 2, 2013 at 8:21 AM, Simon Schick wrote:
>>
>> On Fri, Jun 28, 2013 at 11:20 PM, Derick Rethans wrote:
>> >
>> > Hey Simon,
>> >
>> > PS, please don't top-reply as per mailinglist guidelines:
>> > http://us2.php.net/reST/README.M
Hi!
Building PHP 5.5 with newer compiler on Mac, I'm getting this warning:
/Users/smalyshev/php-5.5/ext/spl/php_spl.c:803:35: warning: format
specifies type 'unsigned int' but the argument has type 'intptr_t'
(aka 'long') [-Wformat]
spprintf(&hex, 32, "%016x%016x", hash_handle, hash
Hi!
I was looking at bug https://bugs.php.net/bug.php?id=65028 and looks
like it happens because phar writes manifest after HALT_COMPILER(); ?>
and first 4 bytes of manifest are manifest length (little-endian), but
when it read the header, it checks if there's \r\n after ?>. So if
length has lowes
