in reply to ActivePERL is the devil?
use Shell qw( perl ); # { local @ARGV = (...); do $filename; } use Shell qw( dir ); # glob() seems enough use Shell qw( copy ); # File::Copy use Shell qw( del ); # unlink use Shell qw( cd ); # chdir
All the advices of the monks who replied to this node still apply. Some refactoring and moving filenames and tasks to configuration metadata driving the script could produce a much more robust and useful tool. But probably this isn't a priority or a need. So just two suggestions: (1) use / everywhere because Perl at Windows understand it very well unlike Windows itself; (2) maybe the Perl scripts "d:/perl/macc1" and "d:/perl/mmac3" can be converted to Perl modules with advantages to maintenance.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: ActivePERL is the devil?
by ikegami (Patriarch) on Jun 08, 2007 at 13:22 UTC | |
Re^2: ActivePERL is the devil?
by naikonta (Curate) on Jun 08, 2007 at 15:24 UTC |