itaps-parallel inconsistencies in getAllVtxCoords

[Tim Tautges]

I'd rather we returned 3*num_vtx, that way apps don't need to call 
num_dimensions and branch on that.  But, I do 3d for everything.  Come 
to think of it, why is it we need to prescribe what is returned? 
There's a size returned for that coordinate array, isn't there?  Then 
the number of dims is coords_size/num_vtx.

- tim

Lori A. Diachin wrote:
> Hi Carl and Tim,
> 
> Right after you left today a question came up regarding what functions 
> such as getAllVtxCoords should return for 2D meshes.   In my and Ting's 
> implementations, we return an array of num_vtx*num_dim but you and Tim 
> seem to return num_vtx*3 regardless of the dimension of the mesh.  The 
> documentation doesn't specify the proper behavior.
> 
> Thoughts?
> 
> Lori
> 
> 

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
          phone: (608) 263-8485      1500 Engineering Dr.
            fax: (608) 263-4499      Madison, WI 53706