>>15
Should work like this
PRE:
a #New forced indentation offset set by this line
b #Will show below a
c #This is not a new block because PRE is speshul
d #Shows below b
e #Syntax error: the forced indentation of content has been violated
Parsing JSON is so simple it's easier to write your own JSON parser (let alone an S-expression parser, a kid's homework) for a language that doesn't come with one, than to using an existing XML parser.
Yes, XML does looks a bit verbose for the toy examples you provide
And for more complex examples it's more complexly verbose. It's not like it'll become more efficient with more tags and documents, you keep repeating every fucking tag when closing it and wasting angle brackets.
especially if it should be portable amongst applications
And what makes XML portable and JSON or S-expressions not?
Sure, that looks halfway decent, except for maybe the STYLE= thing.
I feel the same way; I should have thought of something better for that.
Are S-expressions actually used for much outside of the Lisp world?
When you least expect it:
http://www.oracle-base.com/articles/misc/OracleNetworkConfiguration.php
(Not perfect Lisp fashion, but awfully close.)
Actually, I haven't seen them much outside Lisp (yet there are like two dozen active Lisp dialects including embedded languages), but I haven't seen any other format aside from INI get universal either before businessmen and retards started to circle-jerk to their newly-found enterprise bussiness solution XML.