Re: pod2usage question

[dwhitney]

Hello all, I've changed my BEGIN block, to look like:

#!/usr/bin/perl -w
# 
# $Id: move_data.pl,v 1.12 2005/05/05 21:25:58 dwhitney Exp $

### Declaire script vars ###
use vars qw( $Executable $Transaction @cmd $LIBPATH );
$|++;    # Turn on autoflush

### Import pre-requisite packages
use strict;
use warnings;
use Log::Log4perl;
use Getopt::Long qw( GetOptions );
use Cwd qw( chdir realpath );
use Benchmark qw( timestr timediff );
use File::Basename qw( fileparse );
use File::Spec qw( catfile rel2abs );
use Pod::Usage qw( pod2usage );
### Bomb if there is nothing on the command line ###
pod2usage(2) if ( not @ARGV );

BEGIN {
    $LIBPATH = "../lib";
    @cmd = fileparse( File::Spec->rel2abs( $0 ), '\.[^.]*' );
    $LIBPATH = File::Spec->catdir( $cmd[1], "$LIBPATH" );
    eval " use lib '$LIBPATH'";
}

### Use the MoveDataTools package ###
use MoveDataTools;

Problem is, it still does not display any of the usage info in a Linux env. Good speed increase, but no man or help....
Bummer!

[Anonymous Monk]

Hello all, Same problem, resolved by converting the script file to unix end-of-line with dos2unix.

[planetscape]

Ah, yes. This has given me problems before, often with Unix-style programs operating on DOS-style data. Good to remember to check for these sorts of issues.

In the quest for a utility to convert between *nix and DOS newlines on a regular basis, I have found flip: Newline conversion between Unix, Macintosh and MS-DOS ASCII files to be useful. It not only converts between DOS and Unix file formats, but also includes a handy -t command-line switch to tell you which format a given file uses.

HTH,