in reply to Re^9: To help not to misguide
in thread To help not to misguide

This node falls below the community's minimum standard of quality and will not be displayed.

Replies are listed 'Best First'.
Re^11: To help not to misguide
by Roy Johnson (Monsignor) on Jan 03, 2006 at 15:41 UTC
    If you want to be concise, you don't need to say anything is wrong. It is implicit in the correction, where you say how it's wrong. e.g.:
    possessives like "rat's" should include an apostrophe

    Caution: Contents may have been coded under pressure.
    A reply falls below the community's threshold of quality. You may see it by logging in.
Re^11: To help not to misguide
by Aristotle (Chancellor) on Jan 03, 2006 at 15:43 UTC

    “Having” to be polite has never deterred me from posting corrections. Nor from going to the trouble of making them polite.

    And drop the hyperbole about verbosity. Explaining why a piece of posted code is wrong does not make the node any harder to understand than a curt, snide “wrong!” for those readers who already know, but helps those who don’t.

    Makeshifts last the longest.

      I'm not a native speaker and really have to think what and how I write. And I find a 'XY is wrong.' much easier to understand than a substitution that's intended to not hurt somebody's feelings. 'You are wrong' is a simple and clear expression, that of course should be followed by an explanation of What and Why.

      If a questioner has problems with being told that (s)he is wrong, I don't see that as a problem of the answerer.

      Ordinary morality is for ordinary people. -- Aleister Crowley
Re^11: To help not to misguide
by Anonymous Monk on Jan 03, 2006 at 23:04 UTC
    Tact is the knack of making a point without making an enemy.

    Isaac Newton (1642 - 1727)