Hi Monks

I wrote this little sub, it runs a system command that executes a external package called htmldoc. I did not install the software to see when the software is not running proparly, if it will return anything in $@

When I execute the sub it spools to the screen
'htmldoc' is not recognised as an internal or external command, but $@ is empty. I need the sub routine to return a 1 if it was successful or 0 if there was an error

Please Help

sub html_to_pdf
{
    my($pdffile,$htmlfile)=@_;
    
    $command = "htmldoc --webpage -f \"$pdffile\" \"$htmlfile\"";
    print $command."\n";
    eval{system("$command");};
        print "\$\@:$@\n";
        if($@)
        {
            print "html to pdf Failed->\n$@\n";
            return 0;
        } #if($@)
        else
        {
            return 1;
        } #else for if($@) 
} #sub html_to_pdf

[download]

In reply to Another eval $@ question by PugSA

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.