I think that your example falls under the "Uncharted Territory" category - it is quite possible that what svad wanted to do is impossible, but no-one wanted to stick their neck out on the line and say it is. If svad was not satisfied, svad has every right to let us know.

Personally, i don't think that all questions should be fully answered. I think that the seeker should have to do a little work to find the answer. They certainly will learn more that way. Sometimes a better answer is one that shows another way instead of merely fixing the symptom. I see nothing wrong with the system we have here - what i do have a problem with is users who only read the first couple of replies ... *ahem*

As for your suggestions, i recommend you go download and install the Everything Engine and find out just how difficult implementing such requests can be. Maybe you should get an account at perlmonk.org and offer this service yourself. You would gain some brownie points for sure. ;)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to (jeffa) Re: How to know whether question in SOPW is entirely answered or not? by jeffa
in thread How to know whether question in SOPW is entirely answered or not? by Chicken

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":