in reply to Re: Difference between tr// and s///?
in thread Difference between tr/// and s///?

It's a frightening trend. Whenever someone asks a question, you'll usually get someone replying by copying & pasting perldoc info. In my view, they are trying to look smart by doing so and perhaps get some XP. (Hey, look at me, I know how to use perldoc!)
  • Comment on Re: Re: Difference between tr// and s///?

Replies are listed 'Best First'.
Re: Re: Re: Difference between tr// and s///?
by archangelq (Novice) on Feb 06, 2004 at 23:21 UTC

    While I agree in principle, that's still a harsh critisism.

    Instead, perhaps a comprimise, suggesting the person look in x or y perldoc, and search for z entry? Or a link to the same on http://perldoc.com rather than repasting stuff we all have access to anyway? If someone doesn't know how to look, they should certainly learn, but simply reposting from perldoc isn't going to help.

      If someone doesn't know how to look, they should certainly learn, but simply reposting from perldoc isn't going to help.

      Exactly, at least for the quoted part. And reminding them to look at the docs should not be equivalent to the statement "You're too stupid to look at the docs, so I'm going to punish you by pointing that out and not giving you any other help." So if people post from perldoc (or whatever) instead of linking, they should include how to get the information--hence the content and structure of my post. perlop is a fairly long document (over 2000 lines, or 30 pages). Reposting excerpts does not hurt anyone and provides easy access to the relevant sections of the documentation.

      Some people forget that this is not Usenet. The Monastery is a social network that tries to increase its appeal by putting social considerations on a level with technical ones. So far, it has worked very well.

      --
      Allolex