Redirecting output on win32 from a script called by just its name is broken, see the release notes.
C:\temp>cat foo.pl
#!/usr/bin/perl -l
use strict;
use warnings;
print 'Foo';
__END__
C:\temp>foo
Foo
C:\temp>foo >foo.txt
C:\temp>cat foo.txt
Foo
use pl2bat, shipped with activestate perl. This will wrap your perl-script in a .bat-file, from which redirecting will work;
OTOH I'm new on cmd.exe, I've been on command.com (when using Windows) till just about one month ago, and there I had to use pl2bat, with which for some reason redirecting did not work. Which was a major pita and caused me to implement -i, -o switches for some of my commonly used scripts.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|