-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
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). |
I just dropped pull request #29 in the hopper to provide better error handling in |
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.
The text was updated successfully, but these errors were encountered: