comment on

That's it. Thanks!

Everything is extraced under the $ENV{PAR_TEMP}/inc/. I was able to successfully create a test script using the following:

test.xml

<opt date="test>
  <test>This is a test</test>
  <company id="test" />
</opt>
[download]

test.pl

#!/usr/bin/perl

use strict;
use XML::Simple;
use Data::Dumper;

my $xml = new XML::Simple;
my $ret = $xml->($ENV{'PAR_TEMP'} . "/inc/test.xml");

print Dumper($ret);
[download]

Compiled with: pp -o test.exe -a test.xml test.pl

Moved the PAR package to another directory and ran it. It ran successfully.

I guess for testing, one can check to see if PAR_TEMP is set. If it's not, assume a command line run else assume PAR run, since the PATH to your file will definatly be different based on a PAR or command line run.

-- philip
We put the 'K' in kwality!

In reply to Re^3: "PAR'ing" XML configs? by guice
in thread "PAR'ing" XML configs? by guice

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks