I don't think that is possible without seriously hacking a solution.
PHPTAL works by generating a PHP file from the template, this file is
then 'included', parsed and executed by PHP itself.
So to avoid the creation of those file, the output of PHPTAL should be
kept in a variable and then call eval() with it.
Another option is to create a custom stream wrapper for PHP
(in-memory, SQL, ...) and then modify PHPTAL to use the new wrapper.
Both options will severely hurt PHPTAL's performance, much more if you
have a bytecode cache in place (APC, eAccelerator...).
On Thu, Jul 31, 2008 at 3:18 PM, Alejandro Giardino
<[EMAIL PROTECTED]> wrote:
> I'm using PHPTAL with some forms in a web site. PHPTAL is writing files in
> /tmp as a usual behavior, but I would need to avoid the files creation
> I've red the manual and some mailing list archive and I've tried with
> 'PHPTAL_FORCE_REPARSE' but I couldn't avoid the creation of the files.
> So... is there any way to avoid the PHPTAL intermediate file creation??
> Alejandro Giardino
> PHPTAL mailing list
PHPTAL mailing list