Using php in your template or trying to create 'templates' as above is really not recommended.
why not recommended?
is it slower? no, its faster, no extra parsing layer
is it more complicated? no, there is no new syntax to memorize
is it less robust? no, its more robust, its as robust as php is, while templating systems offer you only a subset of what php does
is it less secure? no, it uses no evals(), which some template systems offer so there is no security issues
my code does not try to "create 'templates'", php is templates already. the other template systems simple are just complicated code which end up duplicating already existant functionality within php...
there is only one thing these templates do that php does not... allow the template to be viewed and edited within a wysiwyg editor
if you are designing a system for your own use (ie programmers) then there is simply no reason to learn the specific syntax and creation methodology of any of these systems...
if you are designing a templated system for non programers (ie designers) then you want to look into one of the other template engines... since they may have no programming knowledge and you may want to restrict the access of what they can and can't do and perhaps put loops and such in a different syntax more to their liking
proponents of the templates want you to use them, and want you to think that they offer the only solution to a problem and might even tell you that not using their system is 'not recommended'