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: [Windows] __out symbol conflict

From: "Danny Smith" <dansmister at gmail dot com>
To: "Benjamin Kosnik" <bkoz at redhat dot com>
Cc: libstdc++ at gcc dot gnu dot org, aaronavay62 at aaronwl dot com
Date: Wed, 13 Feb 2008 07:54:28 +1300
Subject: Re: [Windows] __out symbol conflict
References: <9c03c2dd0802111530u255eb031vf4d4c479d0c643c0@mail.gmail.com> <20080212123511.42e013ba@wabash.artheist.org>

On Feb 13, 2008 7:35 AM, Benjamin Kosnik <bkoz@redhat.com> wrote:
>
> > >> 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
>

I have only seen _z  used as suffix in SAL.  Looking at
http://msdn2.microsoft.com/en-us/library/ms235402(VS.80).aspx
I see that my list may be incomplete.

Danny

References:
- Re: [Windows] __out symbol conflict
  - From: Danny Smith
- Re: [Windows] __out symbol conflict
  - From: Benjamin Kosnik

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