It’s true though that a php extension written in C is always going to be at least a little bit more efficient than similar PHP code.

Thanks for the comments!

I didn’t actually write Blitz; that would be Alexey in the comments above. I just tested it.

However, what you are wanting to do, if it’s not possible in the Blitz documentation, could easily be accompished by extending the Blitz class and overriding the constructor. You could define a template path, then do something like this:

define(TEMPLATE_PATH,”/path/to/template/”);

class tpl extends Blitz {
function __construct($tpl) {
parent::__construct(TEMPLATE_PATH.$tpl);
}
}

Of course, in doing this you are adding additional overhead that will affect the speed of Blitz.

Cheers!

My comment would be in regards to the template file path. I would love to be able to set an absolute path in the php.ini file or set a custom include path via php. This would save a ton of time overall in large implementations from writing:

$tpl = new Blitz(’ui/html/login.tpl’);

to just:

$tpl = new Blitz(’login.tpl’);

I could set the constant as referenced above but that really doesn’t save me anything.

Keep up the great work!