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

`blead -h` not quite matching blead's perlrun manpage

Thread Next
Tom Christiansen
April 27, 2011 19:17
`blead -h` not quite matching blead's perlrun manpage
Message ID:
The perlrun manpage says a few minor things that `perl -h` does not,
which come from perl.c/S_usage().

    % blead -h
    Usage: perl [switches] [--] [programfile] [arguments]
      -0[octal]         specify record separator (\0, if no argument)

Not quite; perlrun now has -0[octal/hexadecimal] there.

      -a                autosplit mode with -n or -p (splits $_ into @F)
      -C[number/list]   enables the listed Unicode features
      -c                check syntax only (runs BEGIN and CHECK blocks)

Not quite; perlrun now says it runs BEGIN, UNITCHECK, and CHECK blocks, and also use statements.

      -d[:debugger]     run program under debugger

Not quite; perlrun says you can also use -dt[:debugger] to run 
threaded program under debugger

      -D[number/list]   set debugging flags (argument is a bit mask or alphabets)

I wonder why we don't accept hex flags here from Perl_get_debug_opts().
That would make specifying the numbers way easier.  I kinda wonder why
we even *can* specify numbers, they're so clunky.

      -e program        one line of program (several -e's allowed, omit programfile)
      -E program        like -e, but enables all optional features
      -f                don't do $sitelib/ at startup
      -F/pattern/       split() pattern for -a switch (//'s are optional)
      -i[extension]     edit <> files in place (makes backup if extension supplied)
      -Idirectory       specify @INC/#include directory (several -I's allowed)
      -l[octal]         enable line ending processing, specifies line terminator
      -[mM][-]module    execute "use/no module..." before executing program
      -n                assume "while (<>) { ... }" loop around program
      -p                assume loop like -n but print line also, like sed
      -s                enable rudimentary parsing for switches after programfile
      -S                look for programfile using PATH environment variable
      -t                enable tainting warnings
      -T                enable tainting checks
      -u                dump core after parsing program

Should -u be marked obsolete, or removed from the summary? 

      -U                allow unsafe operations
      -v                print version, patchlevel and license
      -V[:variable]     print configuration summary (or a single variable)
      -w                enable many useful warnings
      -W                enable all warnings
      -x[directory]     ignore text before #!perl line (optionally cd to directory)
      -X                disable all warnings

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