>>>>> "Andy" == Andy Wardley <[EMAIL PROTECTED]> writes:
Andy> The solution I'd like to see is for ttree (or its replacement) to be able Andy> to define any number of different strategies for processing, copying, Andy> renaming templates, and so on. For example a 'copy' policy to copy the Andy> file only, a 'foobar' policy for processing a page with a particular set Andy> of headers/footers, a 'wizbang' policy defining a different set of Andy> wrapper templates, a 'null' policy for processing a template but not Andy> generating any output (like you require), and so on. Then, you could map Andy> templates to policies either by matching file regexen, looking at a META Andy> tag inside the template, and so on. And at that point, you've reinvented GNUmake. Not only do all applications evolve to the point where they can read email, all templating applications evolve to the point where they can perform make. :) You might want to look at stealing the code from the "pmake" make-substitute in the CPAN. Or reinventing it, I suppose. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
