> :-) Guess it is getting late in England as well then :-)
>
> Anyway...
>
> use strict;
> use warnings;
>
> use Ec;
> use XML::XPath;
> use Data::Dumper;
>
> my $ec = Ec->new or die "Can not create Ec object $!\n";
> my $xPath;
> $xPath = $ec->findObjects('job');
> print Dumper($xPath);
> #my $ha = $xPath->findnodes('//job');
> #print Dumper($ha);
>
> This makes no sense at all....
>
> use strict; # Good no complaints
> use warnings; # Good no complaints
> use Ec; # What is this a home brew module how is this relevant to the rest
> of the code?
> use XML::XPath; # XPath module
> use Data::Dumper; # My all time favorite module
>
> my $ec = Ec->new or die "Can not create Ec object $!\n"; # Creating a new
> Ec object (what ever it might be) and storing this in $ec
> my $xPath; # Declaring a variable called $xPath
> $xPath = $ec->findObjects('job'); # Using the $ec variable to do something
> and storing the returned value in the $xPath variable
> print Dumper($xPath); # Dumping the $xPath variable looking at the above it
> is a neat looking nested data structure
> #my $ha = $xPath->findnodes('//job'); # Hang on a minute, now the $xPath
> variable containing that data structure is used as an object and Perl goes
> Bleh!!! not all that strange is it?
> #print Dumper($ha);
>Ec is either a module written by Electric Cloud for their Electric Commander product that we are using (an API) or is our localized Perl module. It returns XML. I guess neither of us should be posting here. We'll figure it out by ourselves. Going back to read-only with this list. Ken Wolcott
