Stanislav Malyshev wrote:
It means you can run a phar file. How is that so hard to understand.
It is not hard to understand. What seems to be hard to understand is
that the scenario you describe is by no way the only scenario PHP files
run in. Not all applications are single entry point and of those that
are, not all applications are suitable to work in non-filesystem
environment. Thus using phar in applications not specifically designed
for it and in environments which presume files are in filesystem might
prove harder than some think.
So if you are wondering about use cases, the PEAR installer is a good
example. Generally I would say phar lends itself for self installing
applications, but also for applications you run infrequently, that are
not that performance critical (which does not mean you want them to run
extra slow either) and where you want minimal fuss in keeping an
uptodate version.
I do not see phar's be used as the runtime after installation for most
applications of course. But a sizeable number of them could be run this way.
Also it is one of those cases of "build it and they will come". So once
we put this into core, people will take notice, tools will be developed,
others will be adapted to become compatible etc.
Maybe we should for a moment shift the discussion from "if its useful"
(because several half way smart people have said it is), to "is it
technically sensibly implemented". Just give these guys the benefit of
the doubt on the usefulness part and make sure its good on the
implementation part.
regards,
Lukas
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
