On Wed, 18 Dec 2019 17:24:21 +0100 Alexander Kanavin <[email protected]> wrote:
> You can also supply your own definition of ENOATTR, as it doesn't > change. That way lies EVEN MORE madness. I don't have any guarantee that it won't be changed at some point, and... I mean, silly though it sounds to talk about "defined" or "undefined" when working on pseudo, it's *really* not okay for non-implementation code to be defining a symbol starting with a capital E like that. I am not sure why the attr people hate compatibility with existing code, but probably because they're monsters who are motivated only by a desire to crush the hopes and dreams of others. That's usually why people make backwards-incompatible header changes. -s -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
