Hello LAUPRETRE, Tuesday, May 15, 2007, 7:12:27 PM, you wrote:
>> From: Greg Beaver [mailto:[EMAIL PROTECTED] >> This is exactly how phar/PHP_Archive works. For example: >> http://pear.php.net/go-pear.phar contains the complete >> PHP_Archive class, which will fall back to the phar extension >> if available. > But you say in the doc that the stub can contain any code terminated by > an __halt_compiler(); ? I don't understand. If a phar archive is generated > by the phar extension, it does not include the PHP_Archive runtime code, > right ? So, it cannot run without the phar extension installed. Am I wrong Yes, noone hinders you to write PHP_Archieve into your stub when using the Phar extension. >> I am probably unclear with my argument here. After a deep >> review of the source code, it seems to me that PHK is >> basically PHP_Archive with a different file format plus a few >> built in extras and a separate website. In other words, at >> the time you started the PHK project, PHP_Archive was fully >> functioning (version 0.6.0, released on 2005-08-30) and was >> backed by the officiality of being served from PEAR, a >> php.net site. Rather than attempt to inject your interesting >> ideas for the future of PHP_Archive, you seem to have >> actively avoided PHP_Archive and re-invented the wheel. > Actually, there is a reason, PHK was not the first step... The first step > was the autoloader. When it was ready, I started thinking of a sort of jar > feature for PHK. So, of course, I looked at PHP_Archive to see if I could > integrate my autoloader. But, at this time (end 2005), there was not much > documentation and the first tests showed that the PHP_Archive'd package > checked if it was run as 'main file'. When I tried to include it, I got an > error message saying that it had to be the first script to run. So, as I > wanted to make library packages, I started a small project which became > PHK, without 'actively avoiding' PHP_Archive. I also must say that, yes, I > tend to consider that a project whose only documentation is the source > code is not a good development base. Maybe it is too theoritical but, IMO, > a project without any doc is not 'fully functioning' :) Well the limitations you encountered back then are long gone. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
