The change in the [code] tag is no longer retroactive, so old posts will interpret inner tags in code segments, just as before. I will think about something for the newer ones, since you find that functionality useful.
Typically, an italic code tag will look like this:
Typically, an [i]italic[/i] code tag will look like this
Whereas someone's array indexing will look like this: for (i = 0; s[i]; i++)
One is preceeded by whitespace, the other is not. [edit] It is preceeded by an alphanumeric. [/edit]
Of course, this isn't always true... but it may be a useful rule of thumb.
I just reenabled tag processing in both [code] and [output] tags.
I'm not so worried about the [i] thing. It would only show in italics if the code fragment also included the closing tag - which is unlikely in C++. My only concern was that that was a hack - I never intended to allow tags in code segments... but if at the end it's useful, let's use it!
So, how would the output tags be used? HEER EES MY COOODE
Error: HEER not identified
Or... HEER EES MY COOODE [output]Error: HEER not identified[/output]
FOUNDEDED A GLITCH.
That's the result of having the output tag inside the code tag. Now I'm just trying to find out how to do it without having a newline using the new tag.
Now. How do you guys post the tags themselves? I forget.