|Welcome to the Monastery|
This is quite the rash response. You're making yet more assumptions, a course of action which hasn't worked out well for you so far in response to virudinesh. Over the last few weeks many people, including myself, have spent a considerable time talking to virudinesh in the chatterbox, and I've also communicated by /msg. This is context you're unaware of. This issue has been resolved by various people, with various working implementations for several variations of the same question asked in the CB, scratchpad and SoPW.
Every now and then people respond to historic nodes or ongoing sagas like this, where they don't have all the facts to hand, and jump to conclusions. In such cases they rarely land in the right place.
"....making sure EVERYONE else is aware of his mistakes by carefully taking the time to point to his other posts."
You seem to have misunderstood why I linked to their other posts, yet more jumping to conclusions. Working solutions and sensible explanations have already been provided. Pointing out that the core issue is the same as the last time they asked isn't unreasonable. If they had a further question about this, if there's something they didn't understand they're of course free to elaborate on their issue. A repost of the same question with nothing new to add gains nothing, for anyone. This is a reasonable frequent event. There's also nothing wrong with making others aware that this issue has already been discussed by the same person.
"You can be sure that your response to him did not help. It only resulted in his node getting downvoted"
If you've been a user here since 2003 I'd have hoped you'd have learned that post reputation is a fairly meaningless metric. Nodes get voted on for a myriad of reasons. tye and merlyn have some fantastic posts on this topic should you care to search for them. Constructive feedback/peer review of replies/code offerings respectively are the only worth while feedback IMHO.
"I looked into yours"
What sample size I wonder?
"This drives people away from perlmonks instead of encouraging them to keep going with it"
Vitriolic responses, offensive language and code which doesn't actually compile or answer the questions asked could also be contributing factors.
"pretending to help"
"Don't bother responding for MY SAKE. I'll don't have time for this BS."
So you can say whatever you want to people, but they can't reply? If you actually didn't want me to reply you had the choice not to respond to me.