If we run a modern mode script with a gmt.conf file that has compatibility 4 [Default], we may get pointless and confusing messages:
gmt [WARNING]: GMT_COMPATIBILITY: Expects values from 6 to 6; reset to 6.
This is because of these tests:
ival = (int)atof (value);
limit = (GMT->current.setting.run_mode == GMT_CLASSIC) ? 4 : 6;
if (ival < limit) {
GMT_Report (GMT->parent, GMT_MSG_WARNING, "GMT_COMPATIBILITY: Expects values from %d to %d; reset to %d.\n", limit, GMT_MAJOR_VERSION, limit);
GMT->current.setting.compatibility = 4;
}
So when gmt begin initializes and sets up the gmt.conf file it ends up with compatibility (ival) 4. This makes no sense for a modern mode script since compatibility is really only for GMT 4 classic scripts. I think the solution is to ensure that a modern mode script writing a gmt.conf file writes 6 so that we dont get these messages.
If we run a modern mode script with a gmt.conf file that has compatibility 4 [Default], we may get pointless and confusing messages:
gmt [WARNING]: GMT_COMPATIBILITY: Expects values from 6 to 6; reset to 6.
This is because of these tests:
So when gmt begin initializes and sets up the gmt.conf file it ends up with compatibility (ival) 4. This makes no sense for a modern mode script since compatibility is really only for GMT 4 classic scripts. I think the solution is to ensure that a modern mode script writing a gmt.conf file writes 6 so that we dont get these messages.