in reply to XML data extraction

This is the worst kind of question: the "here is what i copy-pastad from slashdot 4 years ago and now i need someone to fix it for free" - kind.
While I can understand the need for quick fixes when deadlines loom and the desire to spend the evening with friends instead of homework, I will not help an OP like that who wants to outsorce us as free developers.


holli

You can lead your users to water, but alas, you cannot drown them.

Replies are listed 'Best First'.
Re^2: XML data extraction
by haukex (Archbishop) on Oct 11, 2017 at 13:55 UTC

    Yeah, we get lots of bad questions here, so I completely understand the general frustration. However, having replied to this poster before, I think snehit.ar is one of the better wisdom seekers: usually provides enough information so the questions can be answered in a fairly straightforward manner, AFAICT takes our advice to write their own code (example) - unless I've missed something and you've found where the code was copied from? Even without that background, the root node is well-formed: sample input, runnable, mostly well-formatted code with only two unnecessary lines, expected output - all the stuff we love to complain about loudly when it's missing ;-) So all that taken together is why I had no problem providing code in this case. (And in the end the fix to the original code turned out to be a two-line patch.)

Re^2: XML data extraction
by snehit.ar (Beadle) on Oct 11, 2017 at 12:21 UTC
    Sorry ,my intend was not like that.
Re^2: XML data extraction
by 1nickt (Canon) on Oct 11, 2017 at 12:53 UTC

    Boy holli, you sure brought a ray of sunshine when you decided to come back around. What is your purpose here?


    The way forward always starts with a minimal test.
      To learn perl and seek help if any one can. Thank you sir.

        My comment was not addressed to you, snehit.ar. You are seeking wisdom in a perfectly appropriate way. 👍 👍


        The way forward always starts with a minimal test.