<div class="gmail_extra">On Mon, Dec 10, 2012 at 10:44 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="im">> E.g. in class alpha:<br>
><br>
> inherit beta<br>
><br>
> alpha_do_stuff () {<br>
> pre_stuff<br>
> beta_do_stuff<br>
> post_stuff<br>
> }<br>
><br>
> But this is a theoretical case, and often we hack around things via<br>
> _prepend/_append rather than doing things like this, so I doubt this<br>
> is actually done anywhere in practice.<br>
<br>
</div></div>With an "EXPORT_FUNCTIONS = do_stuff" in alpha.bbclass, wouldn't that<br>
still work without the intermediaries though?<br></blockquote></div><br>Hmm, yes, good point. Perhaps it was to allow the user to override an intermediate function that might or might not exist?</div><div class="gmail_extra">
<br></div><div class="gmail_extra">E.g. in the <span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px">do_configure calls gnomebase_do_configure calls autotools_do_configure case, the user could override gnomebase_do_configure, without having to know whether or not gnomebase actually defines a configure function?</span></div>
<div class="gmail_extra"><font color="#500050" face="arial, sans-serif"><br></font></div><div class="gmail_extra"><font color="#500050" face="arial, sans-serif">I'm guessing here, but that *could* be why it was implemented this way. In practice, however, we have to know what our classes are doing anyway, most of the time, for a wide variety of reasons. E.g. uses of overrides have to be operated against carefully to avoid your changes being blown away.<br>
</font>-- <br>Christopher Larson<br>
</div>