Version 2.5

I see you have allowed users to choose an output file extension.

Any reason why the class still assumes the input file extension will be php?

my test results:

Using a standard class file of 1,000 lines (34kb)

Execution time of original source: 7/1000 second

Execution time of encrypted source: 10/10000 second

Encrypted file size: 45kb

Only a 3/1000 second difference in execution time, not bad.

Dave

Hm, I know, I'm not sure, I guess it's just generally used most.

I do know there are .php5 extensions, etc. Just never thought about it tbh.

Overall do you think the speed increase is much better tho?

Much better improvement. There is no observable difference between the open source and encrypted files. It will take a very large file before a human can start to see the difference.

If you include a file into a php source file, it can be any extension.

I just figured since you where allowing the user to set their own output file extension, why not allow them to use a file of any extension as the original source.

Dave

Reason behind the outFileExt was to mainly change if they wanted to use .dec. or w.e else. I'm not sure.

Tho I've updated again, and with use of pathinfo, I've had it use the infile's original extension :)