On Fri, Mar 20, 2009 at 3:39 PM, Johan Hake <[email protected]> wrote: > Hello! > > Soon it will be time to shift from ffc.Foo in PyDOLFIN to ufl.Foo. This > should(!?) be quite straight forward to do. > > Then the only ffc releated code in PyDOLFIN would be the jit call in > dolfin.jit.py > > Would it be a point to continue the migration of the whole jit compilation > thing to ufc instead of beeing a part of the form compiler? > > The form compiler could provide a python interface that ufc.jit could use. > For example: > > FC.signature(ufl_form, options = None) > FC.compile_form(ufl_form, options = None) > > where FC is the form compiler. Based on these two functions ufc will return a > form from the cache or call the FC.compile_form to produce code,compile the > extension module and return the compiled form. > > ufc could have a configuration file naming the prefered form compiler and jit > could of course also take option "form_compiler" too. > > Does this make sense? Are the above functions enough? > > If we do this PyDOLFIN is clean from dependencies to a certain form compiler. > > Johan
Don't know, could be a good idea. I'll keep it in mind the next times I work with the SFC code. Martin _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
