Re: [Stlport-devel] include_next, another filename

[<fra...@fr...>]

If you need stuff in native C headers and don't want to pay for an 
indirection through STLport headers, include_next is more direct.

In a perfect world:
- stlport/* headers when included from the outside 
(_STLP_OUTERMOST_HEADER_ID not defined) should only include stlport/stl/ 
counterparts like cstring include stl/_cstring.h which contains any 
workaround and optional imports in STLport namespace.
- stlport/* headers when included internally (_STLP_OUTERMOST_HEADER_ID 
defined) should only forward to inclusion of native header thanks to a 
include_next, no need for STLport workaround of imports.
- stlport/stl/* should only include other stlport/stl/* headers and 
sometimes native headers through include_next

Doing so make STLport headers independent of native headers 
dependencies. It helps making our lib more portable.

Petr Ovtchenkov wrote:
> Hi,
>
> I'm not sure about correctness of include_next directive
> for file with another name. For example, in file stlport/wctype.h
>
>
> ...
> #    if defined (__hpux)
> #      include_next <stdarg.h>  // <----
> #      include_next <wchar.h>   // <----
> #    endif
> #    include_next <wctype.h>
> ...
>
> The same question for few other files.
>
> Thoughts?
>
>   - ptr
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Stlport-devel mailing list
> Stl...@li...
> https://lists.sourceforge.net/lists/listinfo/stlport-devel
>
>
>