In utils.XMLParser:
- if a parameter value in the form of a double is missing, Nan is returned.
- if a parameter value in the form of a integer is missing, 0 is returned.
This isn't a bug per se, but it's an inconsistency that could easily lead to confusion. Annoyingly Integer.Nan does not exist, but Integer.MIN_VALUE or Integer.MAX_VALUE may be appropriate alternatives. Any thoughts?
In utils.XMLParser:
This isn't a bug per se, but it's an inconsistency that could easily lead to confusion. Annoyingly Integer.Nan does not exist, but Integer.MIN_VALUE or Integer.MAX_VALUE may be appropriate alternatives. Any thoughts?