Replace code generation for ufc classes with new framework using utilities from uflacs

[Martin Sandve Alnæs]

While implementing the new coordinate_mapping class and working on splitting up the finite_element evaluate_basis family of functions to support isoparametric elements, I've used a (IMHO) cleaner approach to code generation which should be moved into ffc.

https://bitbucket.org/fenics-project/uflacs/src/8aee7324e074e41397b0c42bc45dd941899c47f1/uflacs/backends/ufc/?at=master

The evaluate basis family of functions will need some more work first.

[Martin Sandve Alnæs]

As discussed on the dev meeting today, moving all of uflacs into ffc is a plan. However moving this part is highest priority.

[Martin Sandve Alnæs]

Related issues: https://bitbucket.org/fenics-project/ffc/issues/87/evaluate_basis-error-for-combination-mixed https://bitbucket.org/fenics-project/ffc/issues/83/add-a-ufc-coordinate_mapping-class-was-ufc

[Martin Sandve Alnæs]

Consider also this https://bitbucket.org/fenics-project/ffc/issues/52/evaluate_dofs-for-expressions-is-sub when looking at evaluate_dofs

[Martin Sandve Alnæs]

The easiest path is probably to just move uflacs into ffc.uflacs, then refactor step by step later.

[Prof Garth Wells]

Removing milestone: 1.8 (automated comment)

[Jan Blechta]

After the release.

[Martin Sandve Alnæs]

I guess this is mostly done now.