Is there a reason why the "logger" library lives in resource/csdk?

It seems to be widely used, and it seems to not have anything to do with
the stack code (csdk) that it is otherwise sharing a directory with.

It "feels" to me, without understanding the rationale, that it would fit
better in resource/c_common... one reason is that the include
directories in c_common are added to the exported construction
environments 'env' and 'common_env', the former is imported almost
everywhere, this would mean anybody who needs logger could get it
without having to add it to its own construction environment since
everybody starts from 'env' or a clone of it.

_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to