bcompiler 関数

連絡先

コメント・バグ修正・機能拡張の提案や、開発を手伝ってくださるという方は、» alan_k@php.net までメールをください。お待ちしています。

bcompiler_load_exe — bcompiler の exe ファイルを読み込み、クラスを生成する
bcompiler_load — bz 圧縮されたファイルを読み込み、クラスを生成する
bcompiler_parse_class — クラスのバイトコードを読み込み、ユーザ関数をコールする
bcompiler_read — ファイルハンドルを読み込み、クラスを生成する
bcompiler_write_class — 定義したクラスをバイトコードとして書き込む
bcompiler_write_constant — 定義した定数をバイトコードとして書き込む
bcompiler_write_exe_footer — 開始位置および exe 形式ファイルのフッタを書き込む
bcompiler_write_file — php ソースファイルをバイトコードとして書き込む
bcompiler_write_footer — コンパイルされたデータの終了を示す文字 \x00 を書き込む
bcompiler_write_function — 定義した関数をバイトコードとして書き込む
bcompiler_write_functions_from_file — ファイル内で定義されているすべての関数をバイトコードとして書き込む
bcompiler_write_header — bcompiler のヘッダを書き込む
bcompiler_write_included_filename — インクルードされたファイルをバイトコードとして書き込む

bcompiler_load_exe

bcompiler

Last updated: Fri, 14 Nov 2008

add a note User Contributed Notes
bcompiler 関数

codeslinger+uph80111 at compsalot dot com
11-Jan-2008 09:16


try this, I believe that it will solve the problem with __FILE__ 



<?php



    eval("\$Foo = dirname(__FILE__);");

    echo "\n<br>FILE = '$Foo'\n";



?>

Albert Kok
24-Oct-2007 04:08


A few notes to succesfully configure PHP5 to load bcompiler.



In case of using Debian/Ubuntu Linux: When installing from the PECL (PEAR) package, make sure you have the php5-dev library installed in your system (apt-get install php5-dev).



Newer versions of Ubuntu may error out while installing bcompiler thru PECL, asking you to reinstall bzip2. This will not fix the installation. Instead, install the libbz2-dev library (apt-get install libbz2-dev) and try installing bcompiler from PECL again.



After installing bcompiler from PECL, don't forget to make sure you load the bcompiler.so library in your PHP configuration for the new bcompiler functions to become available. This is done by adding the following line to the bottom of your php.ini file(s):



extension=bcompiler.so



If you were to use the bcompiler functions thru your webserver, you need to restart it to reload the php configuration.



Regards,

Albert Kok

Sinured
01-Jul-2007 08:57


Regarding alan at akbkhome dot com's note:

Not only __FILE__ will be handled differently; same for errors thrown by PHP:



If the file was compiled from a another file (bcompiler_write_file()), then PHP will blame the original filename - looks very strange when you put a file which was compiled under Windows on an UNIX system.



If the file was compiled by bcompiler_write_[class|constant|function](), error messages will contain the filename of the file which has called these functions.

roberto at spadim dot net dot br
24-Jun-2007 10:33


hello guys, since bencoder don't work for __FILE__ constants i have a bcompiler script working, anyone that want it can send me an email

the source is 100% compatible with original file, the only problem is php5 new function methods that

<?

if (!function_exists('function_name')){

 function function_name()

}

?>

don't work but it's a php5 new method for understand bytecode

cdsheen+bencoder at gmail dot com
25-Jul-2006 05:58


Here's a script to act as a front-end for bcompiler, which may be very similar to the eA ones:



http://bbs.giga.net.tw/bencoder.php



BENCODER v1.1 - Encode your PHP script using bcompiler



Usage: bencoder [-f] -o FILE    file1.php

       bencoder [-f] -o OUTDIR  file1.php file2.php ...

       bencoder [-f] -o OUTDIR  -a SRCDIR  [-s SUFFIX] [-c] [-r]



  -f        : force overwriting even if the target exists

  -o FILE   : the file name to write the encoded script

              (default to '-encoded.php' suffix)

  -o OUTDIR : the directory to write all encoded files



  -a SRCDIR : encode all files in this source directory

  -s SUFFIX : encode the files with the SUFFIX extension only (default: php)

  -c        : copy files those shouldn't be encoded (no by default)

shannah at sfu dot ca
23-May-2006 03:44


>the special constant __FILE__ cannot be handled correctly by bcompiler

> (it will always contain the name of the original file that was compiled).



I would think that this is the preferred behavior anyways since the compilation should be independent from the source code.  I would want to be able to compile any part of my source code without having to worry if any constants will change as a result of it.  Hence it is better for __FILE__ to contain the name of the original file that was compiled.

arplynn at gmail dot com
28-Apr-2006 08:49


PHP seems to choke on trying to compile PHP5 classes with the private, protected or public modifiers. Additionally, when including files with properly compiled classes on PHP5, it works fine but when php tries to exit it throws a segmentation fault.



It's just not a great idea to use bcompiler for anything other than functions on PHP5, at least for now.

tda at example dot com
07-Feb-2006 05:50


Creating a function after checking if a function exists using function_exists will result in a "Zero Sized Reply" error.



this does NOT work any longer:

if (!function_exists("file_get_contents")) {

        function file_get_contents($filename, $use_include_path = 0)

        { ...define your own function here... }

}



Apache returns: "Zero Sized Reply" after compilation.

alan at akbkhome dot com
27-Oct-2005 07:32


Note: 

the special constant __FILE__ cannot be handled correctly by bcompiler (it will always contain the name of the original file that was compiled). There is no known way around this, as it is converted to a string by the Zend engine.

add a note

bcompiler_load_exe

bcompiler

Last updated: Fri, 14 Nov 2008

bcompiler 関数

連絡先

目次