Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43718
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 209.85.221.121 cause and error)
Message-ID: <49E731C3.4050201@chiaraquartet.net>
Date: Thu, 16 Apr 2009 08:25:23 -0500
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807)
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: detecting bad --CLEAN-- sections
From: greg@chiaraquartet.net (Greg Beaver)

hi,

I've noticed that it is very difficult to tell if your --CLEAN--
sections are actually working, so I wonder if it might be possible to
brainstorm ways of fixing this.

A couple of options come to mind that could be considered

- append this code to the end of the .clean.php file: ?><?php echo
"--CLEAN-- works"; ?> and capture the output, then check to make sure
that we see "--CLEAN-- works" in the output.  This would detect fatal
errors (which is the most common problem I find, especially when a
--CLEAN-- section includes a helper file).
- add a --REMOVEFILES--/--REMOVEDIRS-- section where one can specify
relative paths to files or whole directories that should be nixed, and
have run-tests do the removal

The most common usage for --CLEAN-- is to remove files, so I like the
second option personally.

Thanks,
Greg