On Tuesday 14 August 2012 16:39:57 Michał Górny wrote: > On Tue, 14 Aug 2012 12:46:30 -0700 Zac Medico wrote: > > On 08/14/2012 02:44 AM, Michał Górny wrote: > > > As some of you may have noticed, lately introduced 'double include > > > preventions' have caused changes in effective phase functions in a > > > few ebuilds. > > > > Can't that be avoided by putting the EXPORT_FUNCTIONS call outside of > > the ifndef block? The function implementations themselves can be > > inside the ifndef block, since that only need to be sourced once. > > Isn't that an awful kind of undefined behavior? We're already > on a slippery ground assuming that sourced data changes between > inherits. Assuming EXPORT_FUNCS will work some other ugly way is even > worse.
the "other way" is "the way EXPORT_FUNCS has always worked", so it's not like it's anything new for people to wrassl' with -mike
signature.asc
Description: This is a digitally signed message part.
