Re: fem-fenics

[c.]

On 5 Jul 2013, at 12:37, Marco Vassallo <address@hidden> wrote:

> > Subject: Re: fem-fenics
> > From: address@hidden
> > Date: Wed, 3 Jul 2013 08:06:31 +0200
> > To: address@hidden
> > CC: address@hidden
> >
> > > After the discussion we had at OctConf, someone suggested me that I 
> > > should put some dolfin_init() command at the beginning of evert m-file, 
> > > for setting the environment..what exactly does it mean?
> > 
> > this was probably me.
> > You need to register new classes in the Octave interpreter before you can 
> > use them, 
> > see for example the file simple.h in openmpi_ext [1] that defines a new 
> > class derived
> > from octave_base_value to represent an MPI communicator.
> > All functions in openmpi_ext check that the new type is registered and, if 
> > not, they call 
> > the method simple::register_type to do it.
> > I think it would make more sense to have a function to register all the 
> > types at once at the beginning
> > and issue an error when a user tries to use any function in the package 
> > before initialization.
> >
>  
> So our function fem_init() should declare some variable (we say 
> mesh_type_loaded = 1) in the Octave base Workspace which are later passed to 
> the other functions ?

no, it should just register the types in the interpreter.

c.