in reply to Some advice on another's scripts

You done good. The fact you publish something opens you to critisim. Most writers already know that. A good one will evaluate what you say and either change or offer an argument back.

I once contacted an author for training book on IIS about several mistakes. Some he felt where justified and others he thought were simply my opinion. So there is no harm in pointing something out.

If the author gets pissed then he won't be writing long.

Heck I bet even Merlyn gets contacted on stuff he published.

Replies are listed 'Best First'.
Re: Re: Some advice on another's scripts
by defyance (Curate) on Jun 25, 2002 at 19:08 UTC
    What better way to learn than hearing some little(or big) pointers from your peers!

    Seriously, don't worry about it! Have you ever been in a simmilar situation, where you got a bit of a code review? Sure, it is a humbling experience, but at the same time, you feel great to know that someone out there wants to help? Isn't that the beauty of the open source community??(other than sharing with others of course)

    IMHO, you did this guy a favor, and like Marza said, if he gets pissed then he won't be writing long.

    --~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--
    perl -e '$a="3567"; $b=hex($a); printf("%2X\n",$a);'
    --~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--