新聞財經娛樂♬資訊 News Economy

Thanks ambience.  Looks interesting.

You might want to check out HipHop for PHP: http://www.hiphop-for-php.com/wiki/Main_Page

Thats the technology that powers Facebook and makes it scalable. It was developed by FB. HipHop, though, is not the only PHP2C convertor and you may find one that is more suited to your working environment.

greetings duncanb7, ,  PHP is not really a type of coding language that can be mechanically converted to a compiled executable language and then have successful results on anything that is not very simple (IMHO).  PHP uses server WEB tech as it's foundation, and this is NOT a windows program tech foundation. . . .  I found it curious that you said bamcomplie will produce a windows executable, so I went to their web site and read some of it, although it does produce an executable, the purpose of this seems to have PHP bytecode distributed for other people to use on their PHP server, and you deliver this as a windows executable (in order to protect and hide your PHP script files code in php bytecode), ,  as they pointedly say =
"so it's a perfect solution if you want to distribute your application while protecting your source code"

I did not see any thing about running the executable as a functioning executable with user input and output, I think it just unpacks the bytecode as a command line, like an UNZIP program would decompress a zip archive, but I may be wrong, I also went to the Turck MMCache Encode library which does the php bytecode conversion, and there is no way this will run as an executable in windows. And this is terribly out of DATE.

You may need to get a university student to convert your code for you, or actually pay someone to do it.

I've been thinking about this problem further and noticed you didn't answer my question about the users.  If the users are the general public, many of them will object to a website trying to install an executable because it could contain just about anything.  If you are the user, you can trust yourself but I wonder if you are really going to fix the bottle neck by downloading data to the client.  You could be trading a calculation bottleneck for an I/O bottleneck.

When doing optimization, it's important to remember the 80/20 rule (or the 90/10) rule.  80% of your program won't benefit from optimization.  (It won't help to convert it from PHP to C).

The best solution might be to keep most of the PHP code except for the part that does the calculation.  Pass that off to a C program using PHP's exec() function.

Having said all that, this isn't going to help much unless the C code is written efficiently (optimized for speed).  Chances of someone writing a PHP->C converter that automatically does such optimization well is probably really small.  That section of the program should be written, almost from scratch, in C.

Usually the most important part of this process is selecting an effecient algorithm.

I need to know more about this project before I can offer useful advice.

Do the people who will download the executable file in a closed group where they trust you and all run in Windows?  (For instance, if this is just for yourself, then you can easily trust yourself and guarantee you run in Windows).  In any event, who are your clients?

My advice forks dramatically based on your answer.

What is the specific need to convert PHP to exe? PHP can work perfectly fine as a CLI script language, and indeed I use it extensively to perform various office maintenance tasks. Windows and Linux can both then execute the same (as long as folder locations are treated properly from beginning) scripts. I used to code quote a lot of exes in .Net but scripting makes more sense for me now as its far far easier to maintain.