Hi Marco, Interesting project.
The DOLFIN Array class is defined inside the namespace 'dolfin', so it shouldn't clash with the Octave version, unless that is imported into the global namespace in which case that needs to be fixed in Octave. -- Anders On Thu, May 30, 2013 at 01:18:04AM +0200, Marco Vassallo wrote: > Hi everyone, > my name is Marco and I'm working on the implementation of a > Finite Elelment Library for Octave. > The idea is to create wrappers in Octave for Dolfin, in a similar way > to what it has > been done for Phyton. > Octave provides a Python interpreter, but we want to go directly from > Octave > to Dolfin instead of using it. > So, first of all, I need to check the compatibility between Octave and > Dolfin. > I noted that, unfortunately, including in the same .h file both the > Octave and > Dolfin header file generates some error at compilation time because > both > Octave and Dolfin define a class "Array". Does anyone encountered > a similar problem somewhere? > As a first step, we want to write an Octave function for reading > Dolfin mesh (.xml) and converting it into the Octave format. This > function > could be added to the msh package of forge-octave so that we could > also use the features of the Dolfin Mesh class. > I set up a blog for discussions/advices, if anyone of you is interested > [1]http://gedeone-gsoc.blogspot.it/ > Marco V > > Referenser > > 1. http://gedeone-gsoc.blogspot.it/ > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
