The ISO C committee ([ISO/IEC JTC1/SC21/WG14](http://www.open-std.org/JTC1/SC22/WG14/)) has published [TR 24731-1](http://www.open-std.org/JTC1/SC22/WG14/www/projects#24731-1) and is working on [TR 24731-2](http://www.open-std.org/JTC1/SC22/WG14/www/projects#24731-1):

&gt; ### TR 24731-1: Extensions to the C Library Part I: Bounds-checking interfaces
&gt;
&gt; WG14 is working on a TR on safer C library functions. This TR is oriented towards modifying existing programs, often by adding an extra parameter with the buffer length. The latest draft is in document N1225. A rationale is in document N1173. This is to become a Technical Report type 2.
&gt;
&gt; ### TR 24731-2: Extensions to the C Library - Part II: Dynamic allocation functions
&gt;
&gt; WG14 is working on a TR on safer C library functions. This TR is oriented towards new programs using dynamic allocation instead of an extra parameter for the buffer length. The latest draft is in document N1337. This is to become a Technical Report type 2.

## Questions

* Do you use a library or compiler with support for the TR24731-1 functions?
* If so, which compiler or library and on which platform(s)?
* Did you uncover any bugs as a result of fixing your code to use these functions?
* Which functions provide the most value?
* Are there any that provide no value or negative value?
* Are you planning to use the library in the future?
* Are you tracking the TR24731-2 work at all?


All Tr24731 Solutions on Gang of Coders

Total of 1 Tr24731 Solutions

Do you use the TR 24731 'safe' functions?