This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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]

Re: RFC: Mirror system header exposure in libstdc++-v3's headers


In article <20030407110834 dot 1c8282cc dot bkoz at redhat dot com> bkoz at redhat dot com writes:

>> Index: include/c_compatibility/math.h

> Does this mean that you are going to be using the include/c includes as
> well? That would be very interesting indeed.

Well, not really, I inspected all candidate locations based on
find/grep output.  I did not consider whether a region of headers was
actively used.  Sorry to get hopes up.

>>+ #if !defined (_GLIBCPP_USE_C99_EXPOSURE_HOOK) ||
> _GLIBCPP_USE_C99_EXPOSURE_HOOK

> Can you consider _DYNAMIC or _VARIABLE instead of _EXPOSURE_HOOK?

OK, _DYNAMIC it is.

> Other than that, I don't have any objections to what you are doing. Do
> you think it will work the way that you are expecting (the lldiv_t bits
> are the only thing that give me pause.)

Testsuite results improved the way I expected.  Regarding lldiv_t, the
issue is that the system headers just don't expose the type unless
macros are set "right".

> I'm assuming you would compile the library with this macro set to 1, and
> then allow people to switch it off if they are feeling pedantic. I would
> think this would work.

Yes, the _DYNAMIC macros are effectively set to 1 when the library is
built.  I will document that as a requirement.

> Hmmmm. Interesting.

Well, as usual, active need is the mother of invention. ;-)

I will post/commit a final, tested form with Phil's and your input.

Thanks,
Loren


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]