Anders Logg wrote: > On Thu, Oct 01, 2009 at 05:16:46PM +0100, Garth N. Wells wrote: >> >> Anders Logg wrote: >>> On Thu, Oct 01, 2009 at 04:50:20PM +0100, Garth N. Wells wrote: >>>> It would be useful if Coefficient had the eval member functions which >>>> are common to Expression and Function. Coefficient may no longer be the >>>> best name, but are there any objections? >>>> >>>> Here's an example of how I would like to use it: I have a Surface class >>>> which has a function for representing the surface. This can be a >>>> user-defined or a fe function (it cannot change from one to the other). >>>> I would like to store it as Coefficient with an eval interface like >>>> >>>> Coefficient::evaluate(double* values, >>>> const double* coordinates, >>>> const ufc::cell& cell) const; >>> Sure, but shouldn't the eval(double* values, const Data& data) suffice >>> for this? It would be good to avoid too many versions of eval. >>> >> No, because I know the cell. I just want one eval function that takes >> the cell as an argument so that DOLFIN doesn't perform a search. >> >> Garth > > I see, but I'm just saying that Data contains all that information so > you could use eval(values, data). >
OK, that would work then. Garth > -- > Anders > > > ------------------------------------------------------------------------ > > _______________________________________________ > DOLFIN-dev mailing list > DOLFIN-dev@fenics.org > http://www.fenics.org/mailman/listinfo/dolfin-dev _______________________________________________ DOLFIN-dev mailing list DOLFIN-dev@fenics.org http://www.fenics.org/mailman/listinfo/dolfin-dev
