My last change of code:

#!/usr/bin/perl -w
use 5.010;
use strict;
use warnings;
use Cwd qw();
use PDF::GetImages 'pdfimages';

my $path = Cwd::cwd(); 
my $abs = $path.'/file.pdf'; # filepath to pdf file
my $opt = $path.'/processing/'; # new dir for output
my $images = pdfimages($abs, $opt) or die($PDF::GetImages::errstr);
scalar @$images or die("no images in $path");
for (@$images){print "$_\n";}

[download]

Output in commandline is:
"cant resolve /home/auu/Documents/Imag/processing/, should be able to, please notify PDF::GetImages AUTHOR at extractor.pl line 11"

Enough codes make shapes. (Hamidjon)

In reply to Re^2: Documentation of PDF::GetImages is lack of some info concerning the 'optionals' by programmer.perl
in thread Documentation of PDF::GetImages is lack of some info concerning the 'optionals' by programmer.perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.