> > I can see how the option of ( and ) makes some things easier, but I > > would be interested to hear what necessitates the skin-breaking > > /requirement/ for ( and ).
> better integration with the upcoming theme editor through a better > parser. Since the existing parser suffers no such requirement, it seems odd that a better one must! :) Chris
