Okay, for a while the [code] tag has been broken and shows up in the body of posts, like so:
Code:
#include <stdio.h>
int main (int argc, const char * argv[]) {
printf("Hello, World!\n");
return 0;
}
thus leading many people, including myself, to assume that the [code] tag is broken. However, it turns out that there actually
is a code tag, two of them in fact, but for some reason they are named [codeff] and [codex], and appear to do the exact same thing. However, they still remove all indentations, as you can see below:
Using [codeff]:
code:
#include <stdio.h>
int main (int argc, const char * argv[]) {
printf("Hello, World!\n");
return 0;
}
Using [codex]:
[codex]#include <stdio.h>
int main (int argc, const char * argv[]) {
printf("Hello, World!\n");
return 0;
}[/codex]
All the lines appear indented by exactly the same amount. This can make large code snippets confusing to read. In the old design, code snippets used to get a really nice little box that had horizontal scroll bars and everything. Please restore some of that functionality (and rename the tag to [code] again, as it was more intuitive). Thanks!
edit: there is one other problem with the code tags - they don't automatically turn off the vB code parsing for enclosed text. This can be a problem on a Mac-related discussion board, since HFS (including AppleScript, which uses HFS-style paths) and Objective-C are prominent on the Mac OS X platform, and both of them use colons quite frequently, which as a result can accidentally get converted into smilies. This can, of course, be worked around by encasing the [code] tags inside [noparse] tags, but it would be much nicer if this were done automatically.
examples:
code:
set thePath to "Macintosh HD:Users:me
ocuments:file.txt"
[codex]NSData *myData = [NSData dataWithContentsOfFile
athToFile];[/codex]
Fixing these issues would make the forum much more friendly to technical discussions. Please give them your consideration.