[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fem-fenics] interpolate
From: |
c. |
Subject: |
Re: [fem-fenics] interpolate |
Date: |
Mon, 19 May 2014 17:39:37 +0200 |
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.
c.
- Re: [fem-fenics] interpolate, (continued)
Re: [fem-fenics] interpolate, Marco Vassallo, 2014/05/19
Re: [fem-fenics] interpolate, Eugenio Gianniti, 2014/05/19
Re: [fem-fenics] interpolate, Marco Vassallo, 2014/05/19
Re: [fem-fenics] interpolate, Eugenio Gianniti, 2014/05/19
Re: [fem-fenics] interpolate, Marco Vassallo, 2014/05/19
Re: [fem-fenics] interpolate, Eugenio Gianniti, 2014/05/19
Re: [fem-fenics] interpolate, Eugenio Gianniti, 2014/05/21
Re: [fem-fenics] interpolate, Marco Vassallo, 2014/05/21