dolfin team mailing list archive

[A Navaei <axnavaei@xxxxxxxxxxxxxx>]

2009/2/14 Johan Hake <hake@xxxxxxxxx>:
 [snip]
>
>> > Again, you do not want to do this as you then won't be able to use your
>> > overloaded eval function, as the Function will then be treated to be
>> > discrete, i.e., using the coefficients in _vector together with the basis
>> > function in the FunctionSpace to interpolate any eval().
>>
>> Yes, that's why I'm working on wrapping shared_ptr.
>
> Then you should definetly switch to the development version, or you won't get
> it to work ;)

Raw pointers get wrapped fine. I simply tried replacing
dolfin/swig/*.i with the new development versions, but it didn't help.
(%import "swig/ufc.i" is new and the file is missed, is it supposed to
be generated during build?).  Also, I had to comment out the shared
pointer stuff in dolfin.i in order to have raw pointers wrapped. In
the development version, simply importing dolfin.i maps all raw
pointers and std::tr1::shared_ptr to boost::shared_ptr, automatically.

Is there a plan for something like 'nightly build binaries' for
fenics? I do not have access to a powerful machine and building could
be time consuming. In the case that the debian package stuff (.dsc and
.diff.tar.gz) are available for download, I may try building them on
the opensuse build service servers. Finally, maybe trying to release a
new version for dolfin, without waiting for the rest of the fenics
family, isn't a bad idea as there have been many changes.


-Ali

>
> Johan
>