I think I've already run into cases where displaytypes or such were made too DWIM and I've regretting it because a more sensible action became available (and you can replace an error with a good new behavior but backward compat prevents you from easily replacing an ill-advised DWIM action with a more consistent action).

But perhaps a good compromise would be to have node viewcode page include the above link along with the error text so that you could still easily get to the somewhat related "code for the node" but in a way that wouldn't confuse people into thinking that the code actually is part of the node they requested and that could be changed down the road.

- tye        

In reply to Re: Why doesn't 'viewcode' work for type X? by tye
in thread Why doesn't 'viewcode' work for type X? by demerphq

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.