This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [Windows] __out symbol conflict
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: "Danny Smith" <dansmister at gmail dot com>
- Cc: libstdc++ at gcc dot gnu dot org, aaronavay62 at aaronwl dot com, dansmister at gmail dot com
- Date: Tue, 12 Feb 2008 12:35:11 -0600
- Subject: Re: [Windows] __out symbol conflict
- References: <9c03c2dd0802111530u255eb031vf4d4c479d0c643c0@mail.gmail.com>
> >> A few years back, MS added macros __in, __out, __z, and a few
> >> others to the W32 API interface, intended to be used with its
> >> Standard Annotation Language (SAL) extensions for verifying program
> >> correctness. It is used in the Windows system headers, and
> >> intended to be used in user code as well.
> >
> > Do you have a complete list of the added macros?
>
> I don't know if this is complete....
>
> #ifndef MY_SPECSTRINGS_H__
> #define MY_SPECSTRINGS_H__
>
> #define __null
[snip]
Thanks. I don't see __z on this list. Does this mean that it is no
longer in conflict with these SAL extensions?
-benjamin