On Sun, 5 Oct 2008 16:15:46 +0200
Alexis Ballier <aballier@g.o> wrote:
> An eapi.eclass with such functions and lists of eapi & features
> maintained there could help though.

The problem is, 'features' change between EAPIs. For example, all three
EAPIs have src_compile, but it does different things for all three. One
can't assume that a feature working for current EAPIs will carry on
working for future EAPIs, and even if it does there can be other
interactions that break.

> An EXPORT_FUNCTIONS ignoring any function its doesn't know for its
> eapi would help too.

An EXPORT_FUNCTIONS ignoring incorrect usage makes one less place
checking for eclass screwups...

-- 
Ciaran McCreesh