Moving the following lines to above the: require_once WideImage::path() . ‘Image.php’;
seems to fixed it. It’s probably best to put the wideimage exceptions to a sepearte class file?

thanks for the great work.

/**
* Base Exception class
*
* @package Exceptions
**/
class WideImage_Exception extends RuntimeException {}

/**
* @package Exceptions
*/
class WideImage_InvalidImageHandleException extends WideImage_Exception {}

/**
* @package Exceptions
*/
class WideImage_InvalidImageSourceException extends WideImage_Exception {}

As for setting default values instead of unsetting variables, it’s a good idea, and will think about it. It should work in theory, but depends on how everything else in our JS works. Also, unsetting variables makes sure our ad blocks don’t leave any traces behind, so other javascripts are unable to read these values, so it acts as a security measure as well. But as I said, I’ll think this through the next time I touch this. Thanks for the idea.

httpool = {size:1};
ad(httpool);
httpool = {size:2, border: “red”};
ad(httpool);

These are two different object so you don’t need to unset values when checking for property existence.
If I borrow jQuery’s extend function your ad function would look like:
defaults = {
size: 1,
border: “blue”
};
function ad(options)
{
options = jQuery.extend({}, defaults, options);
options.size…
options.border…
}

P.S.
Just crossed my mind, instead of unsetting values just set default ones

I found this out when I was developing our advertising javascript code (the so-called invocation code). There, the user sets some variables, such as:
httpool_publisher_id = ‘1234567890′;
httpool_color_border = ‘#f0f0f0′;
etc.
And then includes our ad-serving javascript, which serves a single ad block with the predefined configuration.

But not all of these variables are required. When a variable isn’t set, the default value should be used. But in order to detect which isn’t set, I have to unset all of them after initializing the ad block, otherwise the values might leak into the next block — by not being set in the invocation code of the next block.

It’s a very specific case and I can’t really resort to namespaces, because it’s user-land code and an industry standard.