dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #24125
Re: What goes in foo_post.i and what goes in dolfin.bar.Foo ?
On Tuesday July 19 2011 14:14:19 Marie E. Rognes wrote:
> On 07/19/11 23:11, Johan Hake wrote:
> > In general things are added to the python modules under site-packages
> > dealing with stuff added at the extra Python layer, for example
> > ufl_element and such. Also methods that are not part of the C++
> > interface are usually added here.
> >
> > In foo_post we try to mimic the C++ interface as much as possible. In
> > function_pre.i we rename function_space to _function_space and
> > reimplement it in function_post.i. These two changes hang together.
> >
> > And as always there are probably lots of exceptions...
>
> Ok, so stuff providing same functionality as C++, but just needing
> redefinition to make the more sense go in foo_post.i, extra stuff go in
> site-packages. Thanks!
Yes!
Johan
> --
> Marie
>
> > Johan
> >
> > On Tuesday July 19 2011 13:50:22 Marie E. Rognes wrote:
> >> I was wondering what makes something go in foo_post.i instead of in the
> >> "explicit" reimplementation in dolfin.bar.Foo.
> >>
> >> For instance: in function_post.i, Function is extended by the method
> >> function_space().
> >> Is there a particular reason why that is added there, rather than in
> >> dolfin.functions.function.Function ?
> >>
> >> Thanks :-)
> >>
> >> --
> >> Marie
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~dolfin
> >> Post to : dolfin@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~dolfin
> >> More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help : https://help.launchpad.net/ListHelp
References