Skip to main content.
October 28th, 2008

php autoload

As of version 5.0, PHP has had the ability to dynamically include required classes as needed - without requiring the developer to manually include all possible dependencies beforehand. This means that in cases where your code execution never touches 39 of the 40 classes in the project, it loads, parses, and runs that much faster.

There is a performance hit for actually having to call the __autoload() method, but if you're in a situation where the hit for executing a few extra comparison calls is unacceptable... you probably aren't developing in PHP in the first place ;)

Almost all of the php I've written in the last 2-3 years uses autoloading, and it has probably saved me hundreds of hours of aggravation.

In most of my projects, the first line of any script or class usually looks something like this:

PLAIN TEXT
PHP:
  1. require_once "/var/www/common/lib.php";

Then lib.php usually reads something like this:

PLAIN TEXT
PHP:
  1. <?
  2. function __autoload( $class ) {
  3.     include_once( "$class.php" );
  4. }
  5. ?>

And that is all that is strictly required to make the magic happen. It is fast, it is easy to understand, it is easy to use. You can use require_once() or include_once() and there is very little meaningful difference.

I've looked around the net and found several other attempts at improving on this simple mechanism. But they invariably overcomplicate things. They attempt to recurse source directories, cache filename->class differences to the filesystem, and otherwise turn what should be a simple filesystem operation that the php environment supports natively into a mess of exception handling and wheel reinvention.

There are obviously theoretical instances where you might want to have more than the one require_once/include_once line... but I've honestly never encountered one myself.

I mean, you could try to throw an exception if the file didn't exist or otherwise failed to load... but nothing will happen. Failure to instantiate a nonexistant class is a fatal error in PHP, and will be handled as such with or without you - preempting any attempt at throwing an exception.

The only thing you can add is a bit of extra diagnostics or maybe logging to a separate location.

Assume that we have a file 'test.php':

PLAIN TEXT
PHP:
  1. <?
  2. require_once "autoload.php";
  3. $frog = new Frog();
  4. ?>

If autoload.php contains a simple simple autoload function that uses require_once(), and Frog.php doesn't exist anywhere in your include path, the results will look something like this:

PLAIN TEXT
CODE:
  1. ammon@kif:~$ php test.php
  2.  
  3. Warning: require_once(Frog.php): failed to open stream: No such file or directory in /home/ammon/autoload.php on line 3
  4.  
  5. Fatal error: require_once(): Failed opening required 'Frog.php' (include_path='.:/usr/share/php:/usr/share/pear') in /home/ammon/autoload.php on line 3

If we had used an include_once() call, the output is similar, but slightly more informative:

PLAIN TEXT
CODE:
  1. ammon@kif:~$ php test.php
  2.  
  3. Warning: include_once(Frog.php): failed to open stream: No such file or directory in /home/ammon/autoload.php on line 3
  4.  
  5. Warning: include_once(): Failed opening 'Frog.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /home/ammon/autoload.php on line 3
  6.  
  7. Fatal error: Class 'Frog' not found in /home/ammon/test.php on line 4

So that's probably a bit more useful in tracking down the error. Require calls don't return anything - they throw a fatal error on failure. Include calls, however, return FALSE on failure and TRUE if the file is (or, in the case of include_once, has already been) successfully included. So you can include_once() and write to a separate logfile (or to the output stream...) if you need more information than the fatal error already provides you.

<rant>

To those who insist on giving your classes and their containing files different names... umm. Wow.

If I have a class called DatabaseConnection, I'm going to put it in a file called DatabaseConnection.php. If I'm working with strange people who somehow don't think that is explicit enough, I might call it DatabaseConnection.class.php and tweak the autoload method ever so slightly to compensate. There's no good reason to put it in a file called projx-database_connection.incl or something. No. There isn't.

If you want to organize your classes into a meaningful directory structure... good for you. Use PHP's built-in include_path ini option. Don't waste time trying to cascade down a directory structure searching for the classes - just make sure your includes are all in a set of reliable locations. You don't actually have to edit the php.ini file and bounce Apache or your php-cgi processes, just define the additional include paths in the same file where you define your autoloader:

PLAIN TEXT
PHP:
  2.     get_include_path() . PATH_SEPARATOR .
  3.     "/var/www/includes" . PATH_SEPARATOR .
  4.     "/var/www/includes/apple" . PATH_SEPARATOR .
  5.     "/var/www/includes/banana"
  6. );

Naturally, you could turn that into some function calls to dynamically register and unregister directories, etc... but at that point, you're probably hurting yourself again. If your codebase is being reorganized enough to make maintenance of the list of include dirs onerous without full time intervention, something else has probably already gone very wrong. At best, the code probably doesn't work anyway, so any brief delay in updating the list can't hurt any more than whatever else is happening.

</rant>

But seriously. __autoload() is your friend. It will help clean up your code if you let it. It can help enforce naming conventions. It can even improve performance... so long as you refrain from using it to shoot yourself in the foot. ;)

Posted by Ammon as play at 4:06 PM EDT

No Comments »

October 27th, 2008

php signals while selecting

So a fairly longstanding gripe of mine has been that PHP fails to execute registered signal handlers when it receives a signal in the middle of a blocking select call. Today, I finally bumped into a situation where I couldn't just change the spec to avoid the situation... and I've finally figured out how to make it work.

The bug has been reported here, where it was ignored for a few months before being shot down and ignored some more as per php dev team regulations.

Sample code given by the reporter of the bug is markedly similar to the situations I've encountered the problem:

PLAIN TEXT
PHP:
  1. pcntl_signal(SIGINT, "sig_handler");
  2. $sock = socket_create_listen($port);
  3. $read_socks = array($sock);
  4. $n = NULL;
  5. $foo = socket_select($read_socks, $n, $n, NULL);

By filling in his blanks, my first test case looks something like this:

PLAIN TEXT
PHP:
  1. <?
  2. function sig_handler($signo) {
  3.         echo "received sig #$signo\n";
  4. }
  5. pcntl_signal( SIGINT, "sig_handler" );
  6.  
  7. $socket = socket_create_listen( 1234 );
  8. $r = array( $socket );
  9. $n = NULL;
  10. while( true ) {
  11.         $foo = socket_select( $r, $n, $n, NULL );
  12.         echo "select returned '$foo'\n";
  13. }
  14. ?>

When executing the script and pressing ^C (which sends SIGINT), the following occurs:

PLAIN TEXT
CODE:
  1. ammon@morbo:~$ php sigtest.php
  2. PHP Warning:  socket_select(): unable to select [4]: Interrupted system call in /home/ammon/sigtest.php on line 13
  3. select returned ''

Ok, so the warning is to be expected, and we can easily squelch that.

The real problem is that the signal handler never runs.

However... for the first time in my life, a response to a php bug report proves enlightening. The dev who answered this ticket provides his sample code and says he can't duplicate the bug. Upon looking at the differences between their code, only one difference stands out:

PLAIN TEXT
PHP:
  1. declare(ticks=1);

The declare(ticks) directive is deprecated as of php 5.3 and will not be with us in php 6.0. Ticks are an unreliable, unpredictable, and generally bad thing in php. I've neither successfully used them nor seen a successful and justified use.

That being said... turning the tick on but not telling it to do anything appears to address the problem of discarded interrupts:

PLAIN TEXT
PHP:
  1. <?
  2. declare(ticks=1);
  3.  
  4. function sig_handler($signo) {
  5.         echo "received sig #$signo\n";
  6. }
  7. pcntl_signal( SIGINT, "sig_handler" );
  8.  
  9. $socket = socket_create_listen( 1234 );
  10. $r = array( $socket );
  11. $n = NULL;
  12. while( true ) {
  13.         $foo = @socket_select( $r, $n, $n, NULL );
  14.         echo "select returned '$foo'\n";
  15. }
  16. ?>

And execution:

PLAIN TEXT
CODE:
  1. ammon@morbo:~$ php sigtest.php
  2. received sig #2
  3. select returned ''

Which is precisely the desired behavior.

I don't know what the performance hit for turning ticks on is, I haven't had time to research this. But I can confirm that by declaring ticks globally, it does work in an OO environment as well:

PLAIN TEXT
PHP:
  1. <?
  2. declare(ticks=1);
  3.  
  4. class signal_tester {
  5.     function __construct() {
  6.         pcntl_signal( SIGINT, array(&$this,"sig_handler") );
  7.         $this->start();
  8.     }
  9.  
  10.     function sig_handler($signo) {
  11.         echo "received sig #$signo\n";
  12.     }
  13.  
  14.     function start() {
  15.         $socket = socket_create_listen( 1234 );
  16.         $r = array( $socket );
  17.         $n = NULL;
  18.         while( true ) {
  19.             $foo = @socket_select( $r, $n, $n, NULL );
  20.             echo "select returned '$foo'\n";
  21.         }
  22.     }
  23. }
  24.  
  25. $test = new signal_tester();
  26. ?>

Executing and hitting ^C:

PLAIN TEXT
CODE:
  1. ammon@morbo:~$ php sigtest.php                                               
  2. received sig #2
  3. select returned ''

After a few minutes of largely unscientific testing, it appears that turning ticks on globally costs a whopping 4 bytes of ram and causes the script to occasionally consume more cpu than the top process I used to monitor it. So... at first glance the cost is pretty negligible and all I can say is that if you ever need to handle signals (SIGTERM, SIGHUP, etc...) from within a blocking select call in php, it looks like declare ticks is the only option for now.

I did the initial tests in 5.1.6, but can confirm the same behavior in 5.2.5. I don't know how the behavior is going to be in 5.3, since I don't run alpha releases on my servers but my gut likes to think that it will continue to work the same for now... and will hopefully not break until 6.0 (when everything else will explode for a few years). Shrug.

Posted by Ammon as howto, php, programming, rant at 1:26 PM EDT

No Comments »