Using <pre> tags means you get to keep the same screen width all the time

But what it also means is that pages can become hideously wide if a piece of code happens to have a long line. <code> tags get parsed by the PM engine which inserts line breaks every 70 characters or so (it depends on your user settings). That's fine for people with big screens, but it's less nice to people on a 640x480.

On the other hand, using <code> tags for all text isn't such a good idea, as it usually means the font is smaller, and it makes the code hard to differentiate from the text.

[ ar0n -- want job (boston) ]

errr... that was meant to say "using <code> tags means you get to keep the same screen width all the time"! *sigh*

edit: btw, <code> tags on my machine are all the same font size.

Zenon Zabinski | zdog | zdog@perlmonk.org

See also Code Tags and here I go again, opening another can of worms... for previous discussions on this matter.

In other words, it looked like this.

It's my understand (so stop me if I'm wrong) that the
<code> tags are meant for code (and output) samples.
There are other tags (like <p> and <br>) that offer
formatting.

I guess <pre> tags are ok.  Maybe I was wrong in my
edit.
[download]

_____________________________________________________
Jeff[japhy]Pinyan: Perl, regex, and perl hacker.
s++=END;++y(;-P)}y js++=;shajsj<++y(p-q)}?print:??;

Per what Ar0n said further on, <code> tags are better because the PM engine parses them differently than <pre> tags and gives the site more functionality, like the download code link.

You were right to point out the gaffe.

Ah, OK. My apologies then. There are other tags like <p> and <br> that offer formatting, but I find it handy to use <code> tags to save me having to type &lt; and &gt; all the time. I was also specifically thinking about output samples - lots of posters paste huge lines which make pages 100s of characters wide, and the stuff they're pasting wouldn't be considered code.