- Joined
- Mar 16, 2015
- Messages
- 11
- Thread Author
- #1
The suggested tags are:
This sort of code would be generated using the following code:
---
The horizontal rule would used to separate subtopics in a more concise manner. As I have just attempted to do with three consecutive dashes.
The suggested way would be to do:
Quite simply put, this adds a horizontal rule.
---
The subcode is primarily useful when referring to names of members or classes in aforementioned code. For example:
Mentioning of the names foo and bar in terms of the code would be more clearly defined through a subcode tag as opposed to italics. Even more so if you like using italics to portray sarcasm or emphasis. This could also be done as simply as replacing the [subcode] opening tag with:
and the subcode closing tag with:
Although, I am unsure of any conflicts this might bring. However, a more 'full' approach would be to perform separate styling (if possible) as the SnackOverflow example has done. This makes the intent even clearer.
The suggested way would of course be:
---
Hopefully these stick, as they can bring along better formatting for longer and more in-depth posts.
Thanks,
~Funky T
- Horizontal Rule
- Subcode

This sort of code would be generated using the following code:
Code:
Horizontal bar:
[hr]
Regular text [subcode]Subcode text[/subcode] Regular text
---
The horizontal rule would used to separate subtopics in a more concise manner. As I have just attempted to do with three consecutive dashes.
The suggested way would be to do:
Code:
[hr]
Quite simply put, this adds a horizontal rule.
---
The subcode is primarily useful when referring to names of members or classes in aforementioned code. For example:
Code:
private int foo = 5;
private final int bar = 5;
Mentioning of the names foo and bar in terms of the code would be more clearly defined through a subcode tag as opposed to italics. Even more so if you like using italics to portray sarcasm or emphasis. This could also be done as simply as replacing the [subcode] opening tag with:
Code:
[font=Courier New]
and the subcode closing tag with:
Code:
[/font]
Although, I am unsure of any conflicts this might bring. However, a more 'full' approach would be to perform separate styling (if possible) as the SnackOverflow example has done. This makes the intent even clearer.
The suggested way would of course be:
Code:
[subcode]text[/subcode]
---
Hopefully these stick, as they can bring along better formatting for longer and more in-depth posts.
Thanks,
~Funky T