line 20 - you have “===” probably meant “==”

$script = isset($script) ? trim( $script[1] ) : null;

to

$script = (isset($script) && count($script) > 1) ? trim( $script[1] ) : null;

Let me know if that works.

http://outline.mindplay.dk

#1. It borrows from PHP syntax, so you don’t have to learn another entire language. Most of the syntax is largely identical to PHP syntax, but without all the brackets and paranthesis, so it’s faster to type and easier to read.

#2. PHP is in deed a template engine - the {$var} syntax is just more legible and faster to type.

#3. Your solution IS faster, but not by much - my engine is around 200 lines of code, which is all that’s loaded, if your template has already previously been compiled. The total footprint of my engine is less 1000 lines of code. The compiled template output looks almost identical to your handwritten templates (which is what I used to use myself…)

#4. My template engine gives you direct access to all PHP functions, operators, classes, etc.

This engine is also not secure, but in my case, this is also not an issue.

I just wanted the convenience and legibility of a template engine whose syntax is optimized for layout logic - PHP’s syntax is more suitable for business logic.

That’s just my opinion, of course, but my engine has saved me lots of time already, my templates are more legible than my old pure PHP templates, and the performance hit is theoretical, at worst. It also includes a hierachical caching engine, which, if you apply it correctly, can make some pages even faster than straight-up PHP!