Исходное сообщение
"Предложение включить в libc новую функцию brexit (Binary Rem..." Отправлено Аноним, 25-Июн-16 20:32
Что характерно, Microsoft тоже не реализовала. Despite more than a decade since the original proposal and nearly ten years since the ratification of ISO/IEC TR 24731-1:2007, and almost five years since the introduction of the Bounds checking interfaces into the C standard, no viable conforming implementations has emerged. The APIs continue to be controversial and requests for implementation continue to be rejected by implementers. The design of the Bounds checking interfaces, though well-intentioned, suffers from far too many problems to correct. Using the APIs has been seen to lead to worse quality, less secure software than relying on established approaches or modern technologies. More effective and less intrusive approaches have become commonplace and are often preferred by users and security experts alike. Therefore, we propose that Annex K be either removed from the next revision of the C standard, or deprecated and then removed. http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> Что характерно, Microsoft тоже не реализовала. > Despite more than a decade since the original proposal and nearly ten > years since the ratification of ISO/IEC TR 24731-1:2007, and almost five > years since the introduction of the Bounds checking interfaces into the > C standard, no viable conforming implementations has emerged. The APIs continue > to be controversial and requests for implementation continue to be rejected > by implementers. > The design of the Bounds checking interfaces, though well-intentioned, suffers from far > too many problems to correct. Using the APIs has been seen > to lead to worse quality, less secure software than relying on > established approaches or modern technologies. More effective and less intrusive approaches > have become commonplace and are often preferred by users and security > experts alike. > Therefore, we propose that Annex K be either removed from the next > revision of the C standard, or deprecated and then removed. > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm
	Введите код, изображенный на картинке: