C/C++

Excited by the the PERL module XML::DifferenceMarkup I've decided to make the same possible in PHP. The new extension xmldiff recently arrived at PECL. It utilizes the libbdiffmark, the library behind XML::DifferenceMarkup. The xmldiff extension can operate on local XML files, strings in memory or DOMDocument objects.

Shortly I needed an IM functionality in a small project. That turned me again to the Phurple project, the first PHP extension I ever wrote. What a pain was to look into the code written by myself about seven years ago . But it has worked, after three days work the phurple is PHP 5.3+ compatible.

I've just wrote a wrapper extension to the TA-Lib - the technical analysis library. It includes over 150 market analysis indicators and some of vector math functions. The ext is primarily intended to help finance software developers to analyse market data with PHP. Nevertheless I think it wouldn't help to forecast the recently blowed Facebooks IPO

There is always something to try out when writing c programs. Sometimes you just want to know if a small piece of code works as expected without having to recompile the whole project. I used to write small programs for this, just like



But the more you program c, the more pieces of code you possibly want to try out. And writing all that wrapping stuff around the snippet you actually want to check isn't really productive. Therefore I came to the idea of a small program which would straight forward compile and run a piece of c code.

There is a new PHP extension I've written to work with Varnish. The extension allows interaction from within a PHP script with a running Varnish instance. For now there is a basic useful functionality such as ban URLs or set/get Varnish configuration. There will be more with the time. For now I would give a couple of examples for the extension usage, as there is not really any docs for the extension here.

Anyone who did unit testing in PHP knows that private methods are untestable. One workaround for this could be to make no private but protected only members and to call methods using a proxy class. Another approach I'd like to present here is a small extension hack.

Hi there,

last week I wrote a PHP port for Joerg Michael's gender program. The program stands for gender recognition based on firstnames and has a base of >40000 firstnames from around the world. I hope the stuff is deserved to be accepted on PECL.

Hey you all (and me too) web developers. The huge important news today is - now we can send IMs from a script running within a web server - isn't it cool? Only one restriction conditioned by libpurple itself is there - use is definitely safe within CGI environment only. The second important news, as you see from the title - the project was renamed to Phurple. Furthermore there are a couple essential changes I was made as refactoring of the code was written so far.

Became interested? Lets look onto most important points in the changelog:

So, new PHPurple version was issued yesterday and is downloadable from sf.net. What's inside:

* PurpleAccount::isConnecting() added
* PurpleAccount::getUserName() added
* PurpleAccount::getPassword() added
* PurpleClient::deleteAccount() added
* PurpleClient::findAccount() added
* PurpleClient::addAccount returns now a PurpleAccount instance (but was null)
* PurpleClient::authorizeRequest() added

The most interesting thing there is of course the remote client authorization.

Today I've maked the second PHPurple release and changed it's status to alpha. The changes, came into it, are:

* fixed zts compatibility
* implemented the loopHeartBeat method
* the runLoop method was changed to set the heartbeat interval
* fixed memory leak on empty alias
* purple.debug_enabled is now boolean

The most interesting on this release is the PurpleClient::loopHeartBeat() story, which is of course implemented with g_timeout_add. Take a look at the new example script to see how it works.

The first pre-alpha is released and can be downloaded at http://sourceforge.net/projects/phpurple/. The common documentation I've started to make was placed to http://phpurple.rubay.de/.

The main features implemented are:

- send and recieve IMs
- fully implemented account dsn like string
- ability to make account specific settings
- basic work with buddy, buddy group and buddy list

The license was changed to the BSD like proprietary license.

An interesting question I had to answer a couple months ago was - how could I compile an executable statically, so then it works on various linux distributions without the need to install some additional libs. Of course, such the executables are bigger as that, which was compiled in order to use the dynamic libs. But if one wanna to have an independent production executable, this is what one could need.

So, I will explain the thing with the help of an example program, which uses ncurses. First I'm creating the project dir, for example:

and so it will be in the future ...

Namely, i had the excellent oo design suggestion from the Alexey on the pecl mailing list (and it is better, than I could invent), and it works fully for php 5.3 and unfortunately partly for php 5.2. So lets take a look on it ... just get the latest version ...

Some time ago i've started to write the binding for the libpurple, the im lib. About 3-4 weeks ago i had a simple functional implementation, which i've presented on php pecl and libpurple mailing lists. Subsequently i've completely revised the whole thing to be OO and would present it again. There is the same minimal functionality implemented, but all is OO. So, lets begin. First install the php development package and get the code: