in reply to Code Blocks

I don't agree with this proposal for the number of Good Reasons other monks have so carefully explained before me.

Many people have noted that the <code> block is being used for more things than containing Perl programs (like now I'm using it for getting a single monospaced font).

It would maybe be useful to add a different <code> tag to mark things that are Perl programs from things that aren't (of course this would raise the problem of fixing or at least dealing with existing nodes, but this is just a way of reasoning).

Replies are listed 'Best First'.
Re^2: Code Blocks
by Aristotle (Chancellor) on Nov 22, 2003 at 08:16 UTC
    This still doesn't address posting snippets that are basically correct but won't compile maybe because of unclosed blocks, or left out function bodies, or the like. And before we think about ways on how to enforce cleanly compiling code, I would like to hear a compelling reason on why we would want to. So far I'm coming up empty.

    Makeshifts last the longest.

[reply]

In Section Perl Monks Discussion