Creating two numberings on the same field is flawed.

[wrtobin]

If we create two numberings on a field:

apf::numbering * a = apf::createNumbering(fld);
apf::numbering * b = apf::createNumbering(fld);

and run different numbering algorithms on them:

apf::naiveOrder(a);
apf::adjReorder(b);

when retrieving numbers from a later on in a program, the values retrieved appear to be those set by the numbering algorithm applied to b.

I'm not certain what the cause for this is, though the underlying FieldBase<int> for each numbering has the same identifying string, which may be relevant, but so far I haven't exactly identified at what level the bug is occuring.

[wrtobin]

This issue might not occur when using the apf::createNumbering(Mesh*,const char*,FieldShape*,int) function instead, I'm looking into that.

[wrtobin]

Okay using the alternate apf::createNumbering() function avoids this issue, but using this workaround means that apf::getField(num) will return NULL.

The bug in the simpler apf::createNumbering() function still needs to be addressed.