This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 02/12/2013 07:55 AM, Paolo Carlini wrote:The fact is, for many, many years we didn't even try to keep the C library in std only. On the other hand the split c_std / c_global is relatively recent (was born in 4.3). Yes, I'm quite confused ;)As I understand it, the difference between c_std and c_global is supposed to be that c_std keeps the C library in std, whereas c_global has it in both std and the global namespace. All the other differences that have arisen between them seem unintended and wrong.Again, the current status is in a sense good because when the _GLIBCXX_HAVE_AT_QUICK_EXIT and _GLIBCXX_HAVE_QUICK_EXIT are defined, thus the system has the functions in its c library, including <cstdlib> makes available the functions in namespace std irrespective of the configury. But then why having c_std in the first place? I'll leave this to Benjamin...
There is, however, a question whether we need c_std at all now that the standard allows the C library to be in the global namespace as well.Indeed. We could maybe imagine do away with c_std in 4.9...
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |