Peter Kriens <[EMAIL PROTECTED]> writes: > It turned out that the ProSyst implementation of Declarative > Services threw an exception if there was a bind method and no unbind > method. I think this is wrong, but I was not up for a fight about it > so I added the unbind method.
Perhaps there could be another switch added that would control whether the bind methods were forced to be symmetric. Consider: binding ::= 'unbind_static:=' ( 'true' | 'false' ) to configure all references, or maybe binding ::= 'unbind_static:=' LIST to configure specific references, though inconsistency is then possible if the list intersects with the "dynamic" set. If reference parameters could themselves take parameters, we could use this: binding ::= 'bind:=' ( 'none' | 'set' | 'unset' | 'both' ) By default, an non-lowercase reference would have a value of "none", a static reference "set", and a dynamic reference "both". Of course, the ProSyst users would need to specify "bind" to "both" for their static references. -- Steven E. Harris
