From: Roy Stogner <roystgnr@ic...>  20050309 03:21:24

Someone (Steffan?) just committed a change turning the constraint coefficient types (in the DofConstraintRow typedef and in the generic FE compute_C?_constraints functions) from double (which should have been Real) and Real into Number. Is this really necessary? Even if we've got Number defined as Complex, all the constraints should still be functions of the Realvalued geometric data. I suppose the projectionbased compute_constraints functions will come up with Numbers for the constraint coefficients, but any imaginary components should just be floating point error. I haven't been running with complex numbers enabled, so I'm just guessing that this change was prompted by some compiler complaints when the new constraint functions tried to downgrade Complexs into Reals. If that's the case perhaps we should just be making those casts explicit (and maybe tossing in assert() statements to verify my "constraints are always realvalued" claim) instead of storing complex coefficients.  Roy 