[FileFormats.LP] add a documentation page and refactor some names #2848
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
And fall down the rabbit hole with respect to the many differences between solvers.
Now that I've played around with Xpress, I wonder if I need to re-re-think how we go about new line handling. Gurobi's parser is pretty weak in comparison.
My justification for spending so much time on this is that people reading LP files actually happens quite a lot, and historically, we have had many issues related to it (and, I assume, many more that aren't reported).
I think a single, great, open-source implementation that publicly documents all the weird differences in solvers is actually pretty useful.