> In this case, it's more likely that the user is missing something
> simple about the basic usage of the package's utility programs -- e.g.
> if a Perl program (let's call it "util.perl") is written in this manner:
>
> #!/usr/bin/perl
>
> while (<>) {
> # do stuff...
> }
>
> and the user simply runs the program at the command line like this:
>
> util.perl
>
> that is, with no file name, and no pipeline or redirection to provide
> data on STDIN for the program, it will "run" indefinitely, until the
> user kills it somehow -- it's just waiting for input data to work on.
>
> Check the documentation for the utility program(s) in question; it may
> just be a matter of making sure that you are using one of the following
> kinds of command line:
>
> cat data.file | util.perl
> or
> util.perl < data.file
> or
> util.perl data.file
>
> Or it may be something more subtle in the usage of the package
> programs -- but it's bound to be just a matter of getting the usage
> right.
Thank you, David. But it is not likely, as I've checked it first with a
small sample, and it did produce results. I'm pretty convinced that I
ran it correctly.
And I have read the documentation. It's actually
>count.pl output.txt input.txt
or
>count.pl --ngram 3 output.txt input.txt
It's not the first time I'm running a perl script.
This archive was generated by hypermail 2b29 : Tue Aug 27 2002 - 18:20:06 MET DST