Towards a better BBCode

cairnarvon@feynman:~$ cat hello.txt
Hello {spoiler /prog/}.

What do you think of my {sup new} syntax for {i {sup B}{sub B}code} based on S-expressions? It supports {b.i.u function composition} and {sup*2 iteration {sub*3 (and nesting, obviously)}}. It uses curly braces {m \{\}} rather than the traditional {b (}parentheses{b )} because that will require less escaping.

{aa No more unmatched or misnested tags!}

I've written a {spoiler.i terrible} FIOC {i.m SexpCode-to-BBCode} translator, which you can find here: http://sprunge.us/KPWB?py
cairnarvon@feynman:~$ python sexpcode.py < hello.txt
Hello [spoiler]/prog/[/spoiler].

What do you think of my [sup]new[/sup] syntax for [i][sup]B[/sup][sub]B[/sub]code[/i] based on S-expressions? It supports [b][i][u]function composition[/u][/i][/b] and [sup][sup]iteration [sub][sub][sub](and nesting, obviously)[/sub][/sub][/sub][/sup][/sup]. It uses curly braces [m]{}[/m] rather than the traditional [b]([/b]parentheses[b])[/b] because that will require less escaping.

[aa]No more unmatched or misnested tags![/aa]

I've written a [spoiler][i]terrible[/i][/spoiler] FIOC [i][m]SexpCode-to-BBCode[/m][/i] translator, which you can find here: http://sprunge.us/KPWB?py

Hello /prog/.

What do you think of my ^new syntax for ^B_Bcode based on S-expressions? It supports function composition and ^{iteration _{(and nesting, obviously)}}. It uses curly braces {} rather than the traditional (parentheses) because that will require less escaping.

No more unmatched or misnested tags!

I've written a terrible FIOC SexpCode-to-BBCode translator, which you can find here: http://sprunge.us/KPWB?py

>>16
harder to make a BBCode parser that uses a universal close tag
Complete nonsense. If you're doing your job of parsing the text correctly, you're already keeping a tag stack. Suppose you used [/] as the "close recent tag" syntax, you just pop the last tag off the stack and output its closing HTML.

Incidentally, >>1's "parser" is awful, inefficient, and error-prone -- much like every amateur script kiddie attempt at writing some text-massaging code; and that's not only because it's wasting tons of processor time and memory repeatedly concatenating immutable strings, rather than building an array and joining it at the end.

>>19
Yes, and that bug stems from the fact that it's plain and simple, horribly written. See also the [o] bug in quoted text, the idiotic behavior of wrapping parts of code blocks in blockquotes if lines start with >, etc. It's a fucking awful parser.