
17 Aug
2005
17 Aug
'05
3:55 p.m.
That works, too, but if someone modifies the file in the future, the ordering might change again. Apparently g++ doesn't care, so it would be easy for a developer to let the same kind of problem back into the code.
I plan to declare them both class-inline as the fix, however I believe that your compiler is at fault here and that the original code was legal, so there's always the possibility of this occurring somewhere in Boost again, especially as no other compiler cares about this. John.