MacFJA comments

Results 79 comments of


                                            MacFJA

PHPUnit coverage shows "EMPTY" for all files

I found what cause the issue. And it had nothing to do with Windows 😅 They are in fact 2 issues. ## PHPUnit coverage XML The coverage xml generated by...

Support for iterable type

Can you try with `master` ? I run a quick test with `master` and release `0.12.0`, on `master` I don't have the issue, but I have it on `0.12.0`

Compile your app into a single binary

There is also http://virtphp.org/ which can _pack_ a PHP version with extension etc.

Compile your app into a single binary

The big difference between virtPHP and PhpBrew (as far as I know) is the fact that virtPHP duplicate the existing (local) PHP version and add PECL, PEAR and composer to...

Compile your app into a single binary

I made some tests with PhpBrew, I have the result: there are some absolute path inside the build PHP, so it won't work outsite the installation path. Maybe I miss...

Compiling on windows adds `#!/usr/bin/env php` to the output

> I thought too but Composer is using the same stub... So I have no idea... @MacFJA did you encounter a similar issue? Yes, I encounter something similar ([See this...

Compiling on windows adds `#!/usr/bin/env php` to the output

@c33s What is the first line of the file `bin/puppet-enc` ? I just look at Composer phar creation, they remove [on the fly](https://github.com/composer/composer/blob/0f373e3249b0d9523c94766d69d47676f190fdb4/src/Composer/Compiler.php#L205) the shebang of there entry file. So...

MacFJA

PHPUnit coverage shows "EMPTY" for all files

Support for iterable type

Compile your app into a single binary

Compile your app into a single binary

Compile your app into a single binary

Compiling on windows adds `#!/usr/bin/env php` to the output

Compiling on windows adds `#!/usr/bin/env php` to the output

Compiling on windows adds `#!/usr/bin/env php` to the output

CSS Component Selector

Performance improvements?