Yes, I saw that and agree. Suggest we leave things as is for ODP v1.0 since it's not a production target and take this as a follow-on work item for next year to figure out an optimal solution for this problem.
Given the typedef presence this means that other platforms will copy the linux-generic API files into their own API directory and replace the typedefs with their own. Perhaps highlighting the replacement area with a row of asterisks or something would make that an easier process to eyeball. Bill On Tue, Nov 4, 2014 at 11:31 AM, Taras Kondratiuk < [email protected]> wrote: > On 11/04/2014 07:24 PM, Bill Fischofer wrote: > >> These files simply describe the APIs, their parameters, and expected >> behaviors. As such they are implementation-independent. The only >> implementation-specific things in them are the typedef definitions, >> which is what we were discussing moving. The sequence of #includes >> should be: >> >> Application Implementation Common ODP API >> >> #include odp.h >> #include platform/.../odp_xxx.h >> (defines typedefs and inlines) >> #include >> common/odp_xxx.h >> (references >> typedefs. If typedefs >> missing or inlines >> conflict, will >> cause compile >> error, >> indicating a problem in >> platform >> understanding of API) >> >> Does this structure make sense? >> > > In a reply to Ciprian's RFC I've tried to explain a corner case where this > structure fails to work. >
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
