octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fem-fenics] interpolate


From: Marco Vassallo
Subject: Re: [fem-fenics] interpolate
Date: Mon, 19 May 2014 18:31:25 +0200




On Mon, May 19, 2014 at 5:39 PM, 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.


Hi, 
following this point I think it make even more sense to follow the suggestion I gave before:

>    - first argument the function or the _expression_ that has to be interpolated
>    - 2nd argument the functionspace or the function where the first argument has to be interpolated

the function that has to be interpolated is in fact our object and the space where we interpolate it is the parameter.
What do you think?
Marco

c.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]