Please, when posting include some (properly trimmed down) quoted text
from the article you're replying to, for reference...
So, are people on google groups to criticize or help people out?
Both, I'd say. Well, as long as to criticize _is_ to help "people"
out.
When someone asks how to do something, they don't want to be told what
they already know. He stated that he would like a script to check for
those two things and mail him the results. So there it is, a script
that does that.
I was _not_ criticizing the fact that you helped him supplying a ready
made script. I was criticizing how _bad_ it was.
If someone asks you to do something in perl, why do you even waste your
time posting a message that says "go to ...perl.com and you will find
some tips.". That's completely unfair to the person asking the question
This is an oft discussed matter here, and my opinion, as well as that
of many others here and elsewhere is that _that_ kind of answer _can_
be the best help that can be given, at least in certain situations.
there's another thread going on along these lines...
because if they wanted to know that they would have asked something
like "Hey, where can I get more information on learning Perl, id like
to write this script to do .... etc".
The point is that they often, as newbies, do not even know that they
can get the information themselves or how easy it is. You know, it's
that story of "give a man a fish..."!
Said this, _generally_ I am one of those that supplies ready-made
solutions even to relatively trivial questions. But I do not claim
that it is the best thing to do and I'm not arguing with those that
give an RTFM-kinda-answer, nay, generally if a discussion about this
starts, then I support their POVs.
But all this has nothing to do specifically with my post of which
yours is a followup...
NOW LET ME SIDE W/ SHERM. I do believe that you should come w/ some
Huh?!?
So instead of criticizing and posting just to have your say in things,
why don't you try and help someone out when they have a problem.
I wrote that script in about 5 minutes to give him something to go
from. Instead of coming on here and complaining about someone who took
Well, I posted in about 10 seconds, because I really hadn't more time,
in that case.
I _do_ apologize because taking this into account, my cmts must have
sounded particularly aggressive. Had I had more time, as I have _now_
I would have included a "pars construens" as well as the "pars
denstruens", or at least explain why the latter was there.
their time to help, why don't you show how you would write it. The main
Ditto as above.
point here is post if you are going to help, if not then don't waste
everyone's time.
What is arguable is wether the kind of help you gave was really
helping.
In fact you will first or later discover that Perl has a bad name in
many respects because of bad programming techniques spread around by
script kiddies et similia.
If you post such code in answer to a newbie's request for help, seeing
that indeed it _does_ work, he will get used to such bad programming
techniques...
Finally, I just don't think the purpose here is to be an almighty
mentor and oversee what is going on by telling people to read posting
rules and trying to be a professor pointing people in the right
direction. This is a place to ask questions about perl to help get your
Still this doesn't have anything to do with my post.
Please note that I quoted properly your article and supplied cmts on
two specific lines of code, albeit harsh ones...
It was up to your intelligence to understand _what_ was being
criticized!
question answered, so if you know an answer to the post then post about
it. It just goes back to common courtesy of answering what you are
I _do_ know an answer to _that_ post. I _may_ have given it, if had
had more time, or I may have not, even in that case. But that's not a
point.
I was commenting on _your_ code, and it did make sense to do so.
The kind of code you posted was more of a shell script written in Perl
than a Perl script. Not to say that using any of the external
programs exectuing commands should be prohibited in general, nay,
indeed in certain cases this ability provides the "best" solution for
certain tasks. But abusing it has no sense. if it must be a shell
script, then write a shell script, else use Perl to do (more
efficiently) what Perl can do perfectly well by itself.
asked. If people are asking a question they are wanting an answer, an
instant solution, unless of course they ask not to be told how to do it
and just be given some tips.
Again, this has been discussed many times here and I'm not discussing
it anymore now, I recommend reading some relevant threads. Your POV is
acceptable but has not universal value. Others' opinions may vary and
their POVs are acceptable too.
Anyway, I am on here to help some people out. The script I wrote gives
him a starting place to do what he is wanting to do. He is new to perl,
and wanted some help, so there ya go. Take it and run with it. I hope
Ditto as above wrt spreading bad techniques.
what I posted has helped you some, despite rude comments from someone
who didn't have the time to post anything constructive. They apparently
were never new to the Perl language at all.
Oh, no, I've been new to Perl, and I still often have the sensation of
being new to it, when I learn something unexpected from posters by far
more knowledgeable than me. But that's another matter, believe me...
I've been new to Perl, but AFAICT I've never had that kind of attitude
many newbies show to have (well, I hope so, but I cannot gurantee
anything - I should check my first posts here)...
Michele
