This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: ummm.... why is there a limits.h file now?
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: ummm.... why is there a limits.h file now?
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 11 Sep 2001 13:01:01 +0200
- Cc: gdr at codesourcery dot com, libstdc++ at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <200109101748.f8AHmg505345@constant.com>
Benjamin Kosnik <bkoz@redhat.com> writes:
| I was looking through bits/c++config, and saw:
|
| // And any CPU-specific definitions.
| #include <bits/limits.h>
|
| Here's what's wrong with this:
|
| 1) limits.h is a "C" compatibility header. Use something besides this,
| say cpu_limits.h. (No point in confusing things, especially since
| glibc has a bits subdir as well.)
You're 101% right -- I missed that that when it went in.
| 2) there should be no includes in c++config, if possible. This should
| just be included in bits/std_limits.h:
|
| #include <bits/c++config.h>
| #include <bits/cpu_limits.h>
|
| Thoughts?
You're right.
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com