If not we could maybe write a yaml parser :) http://yaml.org/ It has no brackets, it is also hierarchical and it supports comments. El lun., 8 de jun. de 2015 a la(s) 5:16 p. m., Sven Van Caekenberghe < sven@stfx.eu> escribió:
On 08 Jun 2015, at 17:03, Damien Cassou <damien.cassou@inria.fr> wrote:
Sven Van Caekenberghe <sven@stfx.eu> writes:
I am not so sure we should add that.
The JSON spec explicitly does not allow comments because of fear of abuse (that the comments would be used to add semantic meaning outside the spec).
really? That's surprising. Comments in configuration files are very important. Even more when the configuration files are templates for new users.
I know some people are using STON in ways that I did not originally anticipate, that is of course cool, but writing configuration files was not the original goal. STON is a version of JSON that is closer to our object model.
Like I said, I will think about it.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill