On Thu, 2024-05-23 at 15:43 +0200, Quentin Schulz wrote: > I was about to comment on the v2 that this should rather be a class :) > Do we have some information on how/why this is the direction the project > should move towards? What are the pitfalls we're trying to avoid, or > benefits we want to gain? Or is this just some better/best practice we > want to go for?
There was a post from me a while back complaining about repeatedly splitting class files into smaller less manageable ones so that people could access some variables without the task/function side effects. I have a belief that more configuration files would help this kind of problem and make classes more specific/focused and usable. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#199836): https://lists.openembedded.org/g/openembedded-core/message/199836 Mute This Topic: https://lists.openembedded.org/mt/106223409/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-