Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should TOML be considered a configuration or serialization format? #27

Closed
alex opened this issue Feb 24, 2013 · 2 comments
Closed

Should TOML be considered a configuration or serialization format? #27

alex opened this issue Feb 24, 2013 · 2 comments

Comments

@alex
Copy link
Contributor

alex commented Feb 24, 2013

Fundamentally this is a question of wehther TOML documents should be treated as secure to parse or not. In practical terms: in languages like Ruby with a Symbol class which is insecure to create from arbitrary strings, should keys become Symbols or Strings?

@benatkin
Copy link

It's designed to be a configuration format, but this is a false dichotomy in my opinion. I think JSON is a better choice. Comments can and should be stored externally.

@mojombo
Copy link
Member

mojombo commented Feb 24, 2013

It's more of a configuration format in my mind. That's what I really want it for. I leave it to the implementor to decide what the best treatment of keys is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants