MPS issue job003633

TitleAMS requires undocumented AMS_SUPPORT_AMBIGUOUS keyword argument
Statusclosed
Priorityessential
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionIn change 181635 [1], RB added the AMS_SUPPORT_AMBIGUOUS keyword argument to the AMS pool class, and in change 181674 [2] he made it required. But this argument is undocumented.
AnalysisIf this keyword argument is to be supported, it must be documented, but in any case it must be optional so as not to break existing programs.

There are three places where the documentation needs updating:
1. mps_class_ams() [3]
2. The table of keyword arguments [4] -- but in fact it's already documented here.
3. Possibly the release notes [5] -- but on reflection I think not necessary.
How foundmanual_test
Evidence[1] <https://info.ravenbrook.com/infosys/cgi/perfbrowse.cgi?@describe+181635>
[2] <https://info.ravenbrook.com/infosys/cgi/perfbrowse.cgi?@describe+181674>
[3] <https://www.ravenbrook.com/project/mps...manual/html/pool/ams.html#mps_class_ams>
[4] <http://www.ravenbrook.com/project/mps/...anual/html/topic/keyword.html#mps_key_t>
[5] <http://www.ravenbrook.com/project/mps/master/manual/html/release.html>
Created byGareth Rees
Created on2013-10-02 14:52:10
Last modified byGareth Rees
Last modified on2013-10-02 15:14:57
History2013-10-02 GDR Created.

Fixes

Change Effect Date User Description
183513 closed 2013-10-02 15:14:57 Gareth Rees Make keyword MPS_KEY_AMS_SUPPORT_AMBIGUOUS optional, with default value false. Update documentation accordingly.