I'm a bit baffled by your update. If people decide to go with your idea, why do you suggest new users should use CODE and not C, when they are equivalent? It would imply there was some danger using C and not CODE, and only experienced people would know how to avoid the pitfalls - but that contradicts you saying CODE and C are equivalent.

While I welcome the idea of not overloading an existing HTML element, I don't see any point in keeping C for people "in the know", but continuing telling newcomers to use CODE. If (and that's a big if) they decide to go with C, the only reason IMO to keep CODE around for some time is to cater older users, as they are used to it.

-- Abigail

In reply to Re: Two quick (and easy?) suggestions for PM by Abigail
in thread Two quick (and easy?) suggestions for PM by Masem

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.