here's my opinion...: (in other words, don't sue if anything bad happens resulting from my birth and onward)

i understand the concern over this. but is it really gonna do anything? most fairly anonymous users (or those that have >20 post counts) don't read the sticky posts. or they may read it afterwords after they post the code. or they may not care anyway. some don't even make an effort to spell correctly.

i would suggest some kind of automatic code tagging system which works sorta-like the bad-language filter. but that's prone to errors because of the many ways people post code. ie:
Code:
#include <iostream>

int main() {
cout << blah << endl;
}
ignoring the include statement, there's the main function. maybe a script could isolate something starting with a bracket until it ends the bracket. but this would ignore the fact that there are many other functions, all which would be enclosed in these tags seperately. most of the time when people post code, it has errors which are meant to be proofread. if the brackets are one of those errors, the code tags act weirdly.

solution? i would suggest putting a code button up with the other vb code buttons. maybe make it bold font, color it brightly and offensively. add a few exclaimation points, maybe a %$%@! symbol. i know there's already a code button, but it's disguised as #. that leaves its meaning wide open.

better yet, just enclose everything in code tags. it'd look sorta neat (in a weird sorta way). it wouldn't distinguish between code and non-code well, but at least the text would be indented.