Andy Ray Terrel wrote:
> On Tue, Oct 6, 2009 at 10:14 AM, Anders Logg wrote:
>> On Tue, Oct 06, 2009 at 10:07:59AM -0500, Andy Ray Terrel wrote:
>>> In previous versions of DOLFIN, a user was able to define a function
>>> (overloading eval) and then use it in several forms, even when the
>>> for
On Tue, Oct 06, 2009 at 10:21:48AM -0500, Andy Ray Terrel wrote:
> On Tue, Oct 6, 2009 at 10:14 AM, Anders Logg wrote:
> > On Tue, Oct 06, 2009 at 10:07:59AM -0500, Andy Ray Terrel wrote:
> >> In previous versions of DOLFIN, a user was able to define a function
> >> (overloading eval) and then use
On Tue, Oct 6, 2009 at 10:14 AM, Anders Logg wrote:
> On Tue, Oct 06, 2009 at 10:07:59AM -0500, Andy Ray Terrel wrote:
>> In previous versions of DOLFIN, a user was able to define a function
>> (overloading eval) and then use it in several forms, even when the
>> forms had different function space
On Tue, Oct 06, 2009 at 10:07:59AM -0500, Andy Ray Terrel wrote:
> In previous versions of DOLFIN, a user was able to define a function
> (overloading eval) and then use it in several forms, even when the
> forms had different function spaces. It seems that currently a
> FunctionSpace gets attache
In previous versions of DOLFIN, a user was able to define a function
(overloading eval) and then use it in several forms, even when the
forms had different function spaces. It seems that currently a
FunctionSpace gets attached to the user function and then I get a
runtime error when it is used in
