Maybe at some point one or more targets didn't have the proper C++ externs in one or more of the included files?
I agree that it makes more sense to have the extern"C" wrapper around only the contents of the osdSock.h files.
On Sep 8, 2011, at 9:59 AM, Andrew Johnson wrote:
> Hi Jeff, Eric,
>
> I noticed yesterday that *all* the libCom/osi/os/<arch>/osdSock.h files have
> #ifdef __cplusplus
> extern "C" {
> #endif
> wrapped around the system #include files. This doesn't look right to me,
> should we (re)move them from around the #includes? This would happen in 3.14.
>
> - Andrew
> --
> Optimization is the process of taking something that works and
> replacing it with something that almost works, but costs less.
> -- Roger Needham
--
Eric Norum
[email protected]
- Replies:
- Re: extern "C" { #include <...> } Andrew Johnson
- References:
- extern "C" { #include <...> } Andrew Johnson
- Navigate by Date:
- Prev:
extern "C" { #include <...> } Andrew Johnson
- Next:
Re: extern "C" { #include <...> } Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
extern "C" { #include <...> } Andrew Johnson
- Next:
Re: extern "C" { #include <...> } Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|