in reply to Re: error comin g like bareword found.where the operator excetped.and number found missing the operator?how to reslove this error?
in thread error comin g like bareword found.where the operator excetped.and number found missing the operator?how to reslove this error?

This node falls below the community's minimum standard of quality and will not be displayed.
  • Comment on Re^2: error comin g like bareword found.where the operator excetped.and number found missing the operator?how to reslove this error?

Replies are listed 'Best First'.
Re^3: error comin g like bareword found.where the operator excetped.and number found missing the operator?how to reslove this error?
by Corion (Patriarch) on Mar 15, 2010 at 17:23 UTC

    We can't help you understand the flow of your application because you haven't made any attempt to show or explain to us what you have. All you do is post the content of some files which do or do not bear any relation to your problems. Maybe ask your colleagues to explain to you the application. They are in a better situation than we are, because they already know the environment, know the usual errors and know what component talks to what other component, and why. Please stop posting configuration files unless you can also post the code that is relevant for the configuration files. Also, if your code+data is longer than 20 lines, nobody will look at it because you don't make the effort of explaining the code in text.

    As an aside, please don't USE UPPERCASE LETTERS, because that looks as if you are shouting. Also, please use <p> tags to bring some structure to your posts, because they look like text run together without any structure.

Re^3: error comin g like bareword found.where the operator excetped.and number found missing the operator?how to reslove this error?
by SuicideJunkie (Vicar) on Mar 15, 2010 at 20:11 UTC

    You should have noticed that the Monks are very willing to help, provided that the seeker has put in some effort and has runnable code that demonstrates the problem.
    The monks are much less eager to help if there is no effort shown, although there will still be some answers among the comments if the question is understood.
    When the question is hard to read and the provided info makes an accurate answer impossible, then it takes a miracle to help you.
    Finally, if you're YELLING and rushing for an answer and ignoring the advice... then you're just digging yourself a deeper grave.

    Please, just:

    1. Stop.
    2. Breathe.
    3. Think.
    4. Define what the actual problems is.
    5. Trace out what is going on and where it goes wrong. (Coworkers who have seen the code before can help a lot here)
    6. Prove that you know where it is going wrong by removing all the other code and showing that the problem still occurs.
    7. When you have narrowed the problem down to just a few lines of code, show that in code tags.
    8. Use paragraphs and sentences to describe the situation and the goal. (<p></p> tags are important here)
    9. Use capital letters responsibly.
    10. Keep in mind the following as you write:
      • You are not the only person in the world with a problem.
      • Registering on perlmonks does not put us in your debt.
      • You are asking not just for free help, but to get paid for having someone else do your job!
    11. Most importantly, don't just look at the replies, but read them and follow them. Why ask for help if you will not accept the help which is offered?