Au contraire. If it all came down to semantics, then close mis-spellings like fcuk, sh1t and others would still be offensive even though the syntax is wrong.

Syntax is structural: rules of arranging symbols (grammar). It doesn't make sense to say that "fcuk" exhibits incorrect syntax: it is a syntactically correct but currently undefined symbol. Sometimes such an undefined symbol can gain some semantic currency due to resemblance (auditory and/or textual) to an existing symbol, but in most such cases the relationship is not synonomous.

Semantics, in natural languages, is always contextual. And meaning is not static, which is why etymology can be interesting and important, but doesn't specify current usage. "Frikkin" may be historically connected to another word that many people would find offensive, yet they don't necessarily find "frikkin" offensive. And "$@#&*S!!" is really just a generic symbolism for offensive curse words originating in children's comics.

We humans are marvelously semantic creatures. We accept "frikkin" as a less offensive generic term, even if there is an undeniable linkage to a more specific (and offensive) term. Note, "Frick You" just doesn't make sense. Why? Someone who really means the specific wouldn't substitute the generic form. My point? "Frikkin" isn't less offensive because it has a less offensive spelling, or a less offensive sound, but because it has a less offensive semantic meaning. And I mean "less" in the subtractive sense: the very act of substituting a word like "freakin" or "frikken" for a word that we all *know*, takes away the specific nature of the substituted word. "Frikken" simply isn't a synonym for the word it is standing in for, and the fact that it isn't makes all the semantic difference.


In reply to Re: Re: Re: Re: How clean is your code by Anonymous Monk
in thread How clean is your code by Vautrin

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.