From: SourceForge.net <no...@so...> - 2007-10-28 01:01:24
|
Development Specs item #1821437, was opened at 2007-10-28 02:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=837763&aid=1821437&group_id=25576 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: For 5.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Frank Kliewe (frank_kliewe) Assigned to: Nobody/Anonymous (nobody) Summary: Equipment PROFICIENCY Token Initial Comment: Original message from: http://tech.groups.yahoo.com/group/pcgen_experimental/message/8006 PROFICIENCY is another token that is a problem due to ambiguity. This is supposed to declare the Proficiency name that is required to use the item. However, the challenge is that this is Type dependent (thus it might be an Shield Proficiency, might be a Weapon Proficiency). The challenge is that the TYPE should not be required to appear before the PROFICIENCY token on the LST line. This is another case where I would like to make the token specific. (... and before anyone asks, no, my claim that CHOICE is unique is not inconsistent with this sharing the same problem model - CHOICE is using Type Safe Constants, and PROFICIENCY refers to PObjects) One could just add a qualifier: PROFICIENCY:WEAPON|Crossbow (Heavy) Thoughts? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=837763&aid=1821437&group_id=25576 |