Re^3: XML::XPath=HASH(0x10c4e230) is persistent

"... anything on the errors?"

You tell me. What have you investigated?

/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/Parser/Expat.pm is on your computer. What's happening at line 474?
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/Parser.pm is on your computer. What's happening at line 187?
/home/jramirez/PayerDownload/SES/backup/ is on your computer. What *xml files did you `find ...` there?
You've invoked find(...) methods. Was anything found? If so, was that data suitable for chaining to subsequent methods? Again, this is data on your computer.

I also see that you've changed your OP without indicating an update. I don't actually know if I'm responding to the original or some later modification.

-- Ken

Comment on Re^3: XML::XPath=HASH(0x10c4e230) is persistent Select or Download Code

Replies are listed 'Best First'.
Re^4: XML::XPath=HASH(0x10c4e230) is persistent by medirecpr (Novice) on Oct 02, 2012 at 22:47 UTC
Yes Ken, I worked on it. I may be posting my progress wrong, appologies for that. I really do appreciate the forum and am working hard at learing perl. I fixed the XPATH construct, from your response I found that I was mixing my $xp with $sesxp. From there, I noticed that the errores were spurting something about "Use of uninitialized value in subroutine entry at..." Which sounded like a problem with the XML itself. Turns out that the problem was that the grep was returning two files. So I fixed that by modifying the construct to make sure only one possible result. I got past that, got a different error.. "Unsuccessful stat on filename containing newline at..", So I chomped it! I'm loving this! Going through the motions really does help. Really appreciate the help!	[reply]

Replies are listed 'Best First'.

Re^4: XML::XPath=HASH(0x10c4e230) is persistent
by medirecpr (Novice) on Oct 02, 2012 at 22:47 UTC

From there, I noticed that the errores were spurting something about "Use of uninitialized value in subroutine entry at..." Which sounded like a problem with the XML itself. Turns out that the problem was that the grep was returning two files. So I fixed that by modifying the construct to make sure only one possible result.

I got past that, got a different error.. "Unsuccessful stat on filename containing newline at..", So I chomped it!

I'm loving this! Going through the motions really does help. Really appreciate the help!

[reply]