Re: [fem-fenics] interpolate

[Eugenio Gianniti]

On 19 May 2014, at 17:39, c. <address@hidden> wrote:

> 
> On 19 May 2014, at 13:51, Eugenio Gianniti <address@hidden> wrote:
> 
>> Since the python interface is already established I would leave the 
>> functionspace in second place, as it is. I can move the function on which to 
>> interpolate as you suggest, for the C++ interface uses a class method, hence 
>> it is different also with current order.
> 
> Please consider that Octave also has its OOP interface.
> In the default branch this is the "old style" OOP matlab interface,
> according to which class methods are invoked as
> 
> method_name (object, ....)
> 
> so that is the direct translation of the C++ line
> 
> object.method_name ()
> 
> into Octave language.

According to this I should probably leave the interface as it is for 
compatibility with the Octave standard. Currently interpolate uses the 
Function, which in your example is object, just as “vector” of the information 
about the function space, then the interpolated result is returned. Could it be 
better to modify the function in order to make it work in a really object 
oriented fashion, I mean saving the result of the interpolation in what we 
called object?

Eugenio

> 
> c.