mbuild provides less-than-useful error message when library name is invalid

[Eric Swenson]

If you invoke mbuild with an invalid library in the .mb segment, the error message you get it not helpful. For example:

Info: validate_info_seg.info IN: foo.info REPLACE;

add_name: vis.info;

yields the error:

ERROR 11: Invalid library name: IN in statement on LINE 5
SOURCE:Info: validate_info_seg.info IN: foo.info REPLACE;

ERROR 05: Unknown clause begins: IN for statement on LINE 5
SOURCE: Info: validate_info_seg.info IN: foo.info REPLACE;
mbuild (read): Improper data in build script file. Parsing build script: >udd>sa>ejs>work>doc-obs>test>test.mb

The invalid library is "foo" or "foo.info". It is not the word "IN".

I would have expected the error message to read:

ERROR 11: Invalid library name: foo.info in IN statement on LINE 5

[Gary Dixon]

Fixed in mbuild_script_.pl1 and mbuild_script_parse_.rd targeted for installation in the first part of MCR10086.