Date: Wed, 2 Apr 2014 19:58:03 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r264042 - in head: include lib/libc/gen lib/libc/include lib/libc/stdlib Message-ID: <743556FF-1473-4795-8419-80A8A3D22D13@FreeBSD.org> In-Reply-To: <20140402172445.GQ21331@kib.kiev.ua> References: <201404021607.s32G7mhw051355@svn.freebsd.org> <20140402161845.GP21331@kib.kiev.ua> <76A3F92F-18CB-4A9A-8CF5-3A86035C55BB@FreeBSD.org> <20140402172445.GQ21331@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Apr 2014, at 18:24, Konstantin Belousov <kostikbel@gmail.com> = wrote: > It does, I read it. Read the code again. Or even just read the comments. In particular the = blocks_abi.h file contains a detailed description of why the rest of = what you say is wrong. > Now libc depends on the non-standard ABI Not true, the ABI is documented and is as standard as the C++ ABI. We = have code in ports and in the base system that relies on this ABI = already. > of non-standard C extension, The extension is non-standard, however (if you'd read the code, or the = comments in the code you'd already know that) the code in libc does not = require this extension to exist. > implemented by only one compiler. Actually, by two, both of which are in the base system. Well, three if = you count Apple-GCC as different from FSF-GCC. Oh, and a couple of = proprietary compilers. All of which are only required for *callers* of = these functions. libc itself still builds correctly (and is tested = building) with compilers that don't support blocks. If you have helpful comments, then I suggest you try to phrase them in a = less confrontational tone. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?743556FF-1473-4795-8419-80A8A3D22D13>