On Mon, 2004-02-09 at 15:15 -0800, Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
gozer 2004/02/09 14:20:53
Modified: t/conf extra.last.conf.in Removed: t/conf perlsection.conf Log: To test recursive/re-entrant <Perl> sections, autogenerate the included file instead of having to keep t/conf/perlsection.conf in CVS
[...] This causes:
[Mon Feb 09 15:15:10 2004] [info] 5 APR:: modules loaded
[Mon Feb 09 15:15:10 2004] [info] base server + 15 vhosts ready to run tests
waiting 120 seconds for server to start: 00:03#
# writing file: /home/stas/apache.org/mp2-mutex/t/conf/perlsection.conf
waiting 120 seconds for server to start: 00:06# removing file: /home/stas/apache.org/mp2-mutex/t/conf/perlsection.conf
Use Apache::TestConfig::writefile instead?
I did notice that, but I ended up liking it, as perlsection.conf is created, included & then deleted right away, just sufficient for the test. No leftover perlsection.conf file left lying around.
yeah, but it totally messes up the startup messages.
What's the advantage of using A::TC::writefile instead ?
It doesn't cleanup the files and doesn't log what it does. I see no reason why would you want to delete it. t_write_file is for the test run-time.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
