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

ini vs properties #26

Open
utoddl opened this issue May 20, 2017 · 2 comments
Open

ini vs properties #26

utoddl opened this issue May 20, 2017 · 2 comments

Comments

@utoddl
Copy link
Contributor

utoddl commented May 20, 2017

Could you comment a bit about the differences between ini.jsf and properties.jsf? From what I've read, "properties files" are mostly a rebranding of "ini files". I'm considering some changes to ini.jsf, particularly in how it deals with errors. (it seems to handle correct .ini files just fine.) Before I start working on it, I'd like to make sure I understand the contexts of these two .jsf files, as they seem to cover largely the same problem space. Thanks.

@cmur2
Copy link
Owner

cmur2 commented May 20, 2017

Yes, these syntaxes are mostly the same given that they deal with key-value files but have some differences like sections (ini), details about characters used as separators or to start a comment and the explicit check for unicode escape codes (properties). I think both of them handle their respective (simple) syntaxes fine since I do not know any breaking cases. Also the error handling is on the same level (but could be further improved, as always).

@utoddl
Copy link
Contributor Author

utoddl commented Sep 9, 2017

I just dropped pull request #29 in the hopper to provide better error handling in .ini files.

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

2 participants