sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

update package description

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@176304 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
val khokhlov 2005-01-02 16:09:14 +00:00
parent 4b2e48e611
commit 43ae92eaed
1 changed files with 19 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
reference/bcompiler/reference.xml
View file

@ -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