On 07/18/2013 04:20 AM, Alexey Zakhlestin wrote:
On 18.07.2013, at 12:38, crankypuss <fullm...@newsguy.com> wrote:
I've been using PHP for linux command-line applications. Some are quite large.
I've built the code to combine the mainline plus everything it calls into a
single file to avoid portability issues with include libraries. I've built the
code to compress the resulting file using gzdeflate after optionally stripping
comments and excess whitespace.
didn't you just reinvent the PHAR?
I think not, though on the surface there are similarities.
Rather than conveniently including an entire directory full of code that
is mostly unused, I'm including only the code that *is* used, and other
functions of the program that does this include getting a call-tree,
listing references, and so forth; the function of collecting all the
actually-used code into a single file is only a small part of the whole.
And strange as it may seem, this whole project is only an interim
measure on the way to something that might be quite different.
Thanks for mentioning Phar though, as Terry mentioned it might be useful
in compressing/executing the single-file application, though I haven't
yet figured it out to that extent.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
