Thanks for your bug report!

I'd prefer an "MPS expression" comment, because this seems to be a typical
example where not using the abbreviation is uncommon for insiders and confusing
for people who don't know how to deal with these files.

Maybe you could explain me what does "MPS" (expanded) means, I couldn't find its
precise relation to the "Linear and integer program expression format" terminology?

MPS (Mathematical Programming System) format is a de facto standard file format
for storing data used in linear and integer programming (classes of optimisation
problems in mathematics).

For details on MPS, see http://en.wikipedia.org/wiki/MPS_%28format%29 . For
background on linear programming, see
http://en.wikipedia.org/wiki/Linear_programming .

Do you have magic for this?

MPS files usually start with "NAME", historically capitalized - but the match should actually be case-insensitive as the file format supports both uppercase and lowercase. I'm not sure whether we should introduce an "istring" matchlet type for this, or whether matching both "NAME" and "name" should be enough for now.

(1) Is it required, that the NAME field has an entry? Following the specs I found the entry begins at offset 14. If this field must have a value, we could search for "NAME" followed by 10 spaces as magic pattern - optionally followed by searching a newline between offset 15/16 and 61.

(2) Are lower- or mixed-case (seems this is also allowed) field names very common today?

Any news on this?

No updates from the reporter in 2 years, closing.