I hope I haven't asked this one before:
Does it create any kind of ABI issue if one moves
a class method's code implementation from the .H file
to the .cxx file? (ie. doesn't change the calling params
or return value, just moves the code from one to the other)
I'm sure the compiler/linkers handle this 'the right way',
but it occurs to me I'm not sure what the compiler does when
code is implemented in the .H; does it get compiled each time
it's #include'd, then sorted out at link time?
If so, in the case of a class that's entirely implemented in a .H,
what happens when an app is built against a new version of the lib,
but runs in an environment that dynamically links against an older
version of the lib?
I imagine the runtime link is going to choose only one implementation
of the method code, and use it consistently for both the lib and the
app code that uses it, and I /imagine/ it chooses code that was built
into the lib? (So that the runtime lib controls which version of the
code is used, and not some mix of new and old code?)
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
