That mostly answers my questions but leaves one important issue open. If I have indices (1, 3, 5) referring to non-null class objects and specify a size constraint of 3, is that an error? I am not "resizing" but would be "reorganizing" the indices. From a user perspective, this doesn't require class construction so if we define it to be illegal (equivalent to requiring class construction) then this needs to be made explicit. If this is legal then I would wonder about the rules for determining the reinsertion order. At the same time the LRM should clarify whether it is legal if the indices were already (0, 1, 2). Gord. Arturo Salz wrote: > Gord, > > Your example should end up with an array of size 3, whose indices are > (0, 1, 2), and the contents are randomized according to any constraint. > That's why I wrote that constraining the size of an associative array > can be treated in the same way as a dynamic array. > > If the element type is a class type then the array cannot grow in size > because the solver doesn't know how to create the additional objects. > Object creation as part of the constraint solution is a whole different > discussion, which would lead to several enhancements. > > Arturo -- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.comReceived on Wed May 17 13:34:44 2006
This archive was generated by hypermail 2.1.8 : Wed May 17 2006 - 13:35:04 PDT