develooper Front page | perl.perl5.porters | Postings from April 2007

Configure cleanups

Thread Next
H.Merijn Brand
April 18, 2007 04:23
Configure cleanups
Message ID:
In change #30919, Nicholas added some cleanups for 'try'. He however did
not catch all, which isn't his fault, but unveils a somewhat unclean
state of affairs.

There are several approaches to the cleanup.
The common flow of control is to write the test program in try.c, then
compile it, if that succeeded, run it, read the exit code, and clean up.

But the cleanup's are a mess. Here's the possible used combo's:

$rm -f core core.try.* try.core
$rm -f core try.core core.try.*
$rm -f try.*
$rm -f try*
$rm -f try.c
rm -f try.c a.out
$rm -f try.[co]
$rm -f try.* core core.* *.core *.core.*
$rm -f try.c try
$rm -f try.c try.o'
$rm -f try.c tryout.c'
$rm -f try$_exe try.c;
$rm -f try$_exe try.c core core.* try.core;
$rm -f try.h
$rm -f try.* .out
$rm -f try try.*
$rm -f try.* try
$rm -f try try.*
$rm -f try try.c
$rm -f try try.* core
$rm -f try.* try core
$rm -f try.* try core core.try.*
$rm -f try try.* cplusplus$$
$rm -f try.* try$exe_ext
$rm -f try try.* glibc.ver
$rm -f try try$_o
$rm -f try try$_o try.c
$rm -f try try.* .out core
$rm -f try try.* .out core head.c mtry
$rm try.*

I'm thinking about creating a macro that does something like

cleanup_try="$rm -f try try$exe_ext a.out try.c try.o .out core core.* try.core"

for extended cleanup's,

$cleanup_try head.c mtry

should still work.
This however is a huge task. Any objections before I start?

H.Merijn Brand         Amsterdam Perl Mongers (
using & porting perl 5.6.2, 5.8.x, 5.9.x   on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.0 & 10.2, AIX 4.3 & 5.2, and Cygwin.  

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About