cvs: phpdoc /en/reference/bcompiler reference.xml

val Sun Jan 2 11:09:14 2005 EDT Modified files: /phpdoc/en/reference/bcompiler reference.xml Log: update package description http://cvs.php.net/diff.php/phpdoc/en/reference/bcompiler/reference.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/bcompiler/reference.xml diff -u phpdoc/en/reference/bcompiler/reference.xml:1.1 phpdoc/en/reference/bcompiler/reference.xml:1.2 --- phpdoc/en/reference/bcompiler/reference.xml:1.1 Fri Aug 13 10:26:44 2004 +++ phpdoc/en/reference/bcompiler/reference.xml Sun Jan 2 11:09:14 2005 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.1 $ --> +<!-- $Revision: 1.2 $ --> <reference id="ref.bcompiler"> <title>PHP bytecode Compiler</title> <titleabbrev>bcompiler</titleabbrev> @@ -11,7 +11,8 @@ <para> Bcompiler was written for two reasons: <simplelist> - <member>To encode some classes in a proprietary PHP application</member> + <member>To encode entire script in a proprietary PHP application</member> + <member>To encode some classes and/or functions in a proprietary PHP application</member> <member> To enable the production of php-gtk applications that could be used on client desktops, without the need for a php.exe. @@ -20,6 +21,16 @@ </simplelist> The first of these goals is achieved using the <function>bcompiler_write_header</function>, + <function>bcompiler_write_file</function> and + <function>bcompiler_write_footer</function> + functions. The bytecode files can + be written as either uncompressed or plain. + To use the generated bytecode, you can simply include it + with include or require statements. + </para> + <para> + The second of these goals is achieved using the + <function>bcompiler_write_header</function>, <function>bcompiler_write_class</function>, <function>bcompiler_write_footer</function>, <function>bcompiler_read</function>, @@ -35,10 +46,12 @@ exe file. </para> <para> - bcompiler is unlikely to improve performance very much, as it only - bypasses the compiler stage of the PHP running process and replaces it - with the import process in bcompiler. It also does not do any bytecode - optimization, this could be added in the future. + bcompiler can improve performance by about 30% when used with uncompressed + bytecodes only. But keep in mind that uncompressed bytecode can be up + to 5 times larger than the original source code. Using bytecode + compression can save your space, but decompression requires much more + time than parsing a source. bcompiler also does not do any bytecode + optimization, this could be added in the future... </para> <para> In terms of code protection, it is safe to say that it would be impossible