I’m not proposing that the object store fXbins in the case of fixed bins, but rather that an array be generated on the fly for the user that matches the edges instead of simply providing a null array that indicates there are no edges.
Also, it seems like a mistake to use the bin edge container as a test to see how the edges were defined. A simple Boolean would be better and wouldn’t add much weight to this class.
I’m not a huge fan of a method to switch back and forth as the. The user still needs to know how the axis was declared initially. It seems to me that if I get an axis object all methods should work no matter how it was created.