Anthony Liguori <anth...@codemonkey.ws> wrote: > How about we compromise and add a: > > MigrationState *migrate_get_current(void);
I can agree with this one. > I'm strongly opposed to propagating direct usage of a global. If it's > at least a function call, that's a bit nicer. What I am against is with trying to "hide" the fact that we are using a global. function accessor looks ok enough.
