The only problem with that approach is that you have to distribute the php executable and your program is loaded using a command line similar to:
Php -par someapp.par Instead of simply: ./someapp I know this is a small difference, but it makes a big difference when you are dealing with customers who are, how should I say this, not as computer savy as they should be. Jeremy -----Original Message----- From: Simeon Koptelov [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 10:37 AM To: [EMAIL PROTECTED] Subject: Re[2]: [PHP-DEV] PHP compiler Hello Jeremy, Wednesday, August 6, 2003, 8:16:49 PM, you wrote: JSJ> No that is not what I meant. What I meant is so when you write an JSJ> application using PHP-GTK you could distribute a single executable JSJ> instead of the current method. Personally the current method JSJ> doesn't bother me, but to a laymen user it is not what they are JSJ> used to and causes issues. I am not looking for a speed improvement JSJ> really, just a useability improvement for those who choose PHP is JSJ> equally as suited to desktop applications as it is to web JSJ> applications. JSJ> Jeremy Then the jar-like archives is all that we really need :) And in web apps this will be very handy too. There's no need in PHP code compilation in this case -- you simply pack all package files and dirs in one archive using tar+bz2 or zip or something else. -- Best regards, Simeon mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
