This is an example of a post in which it is a bad idea to use CODE tags to protect a [ or a ] in some text.

I have now used those characters inside code tags to protect them, but lo and behold, now i want to post some acctual code for people to run...

#!/usr/local/bin/perl -w
while (<>) {
  my @foo = do_stuff($_);
  print $foo[1];
}
[download]

...I might even break up my program, with more natural text -- which describes the program I'm writting, and in which i may also want to use a [ or a ] (which i have again embeded, using CODE tags). A reason I might want to use them in my descriptive text is that maybe I want to mention what is so great about $foo[1] (there againn, i've used [ and ] inside code tags in my paragraph.

Now i'll finish the real code in my post...

sub do_stuff {
    return split /a/, @_;
}
[download]

Now, if people click the "d/l code" link on my post, they won't be able to run the code they download, because it will have some extra [ and ] characters at the begining and end, and even an extra $foo[1] (or maybe two)

If I hadn't used your suggestion of CODE tags arround the brackets, and i'd used the character entities instead, then people clicking the "d/l code" link would have had a happpy little proogram they couild run, without any changes.