Anas Nashif
Anas Nashif
nice. would be great if this feature is presented in the arch wg to get more feedback and input.
This has been open for months without activity at all and without further reviews, so it was not clear where it was going. We need more reviews here and testing...
> which status change are you referring to ? status change from what seemed to be a completely abandoned PR with pending change requests (stale bot marked it stale just...
> sorry, I had missed that comment. I do not blame you, all I can see in this PR is: 
> at least this long and horrible list of noise 🙈 shows that the feature is cherry-picked into NCS because it's used downstream. Thus it's actively being tested, besides the...
another option: - `zrt_`
Note the emphasis on long-term in the proposal. Goal is to agree on the prefix and start migrating to it slowly, starting with new APIs being introduced in the tree,...
> Also worth to keep in mind that C reserves (some) identifiers starting with underscore: [open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf](https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf) this is how threadx and others are using something like _tx_ or _txe_, so,...
> > why not drop the z completely, i.e. now we have z_tls_data_size, i think _tls_data_size works > > Just adding 1 `_` before functions is very likely to hit...
> We have a single address space while linking. There is no such a thing as "internal" to Zephyr if it is linkable from other Zephyr areas. > A function...