Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: missprint in include/rw/_mutex.h ?
Date: Fri, 10 Aug 2007 11:54:15 -0600
Message-ID: 
 <C8506D6098A6F545BA3745D0CE359E83017579F3@qxvcexch01.ad.quovadx.com>
In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE6438C917C0@epmsa009.minsk.epam.com>
Thread-Topic: missprint in include/rw/_mutex.h ?
Thread-Index: AcfbVnwx0/ul2dXFSoOo0CqmrN9cRwAHzGgA
References: <7BDB2168BEAEF14C98F1901FD2DE6438C917C0@epmsa009.minsk.epam.com>
From: "Travis Vitek" <tvitek@quovadx.com>
To: <stdcxx-dev@incubator.apache.org>


Well, as it stands the macro is doing exactly what its name indicates it
will do. If it is defined, the implementation will not use forward
declarations of the critical section struct and its functions.

I agree that this is a little weird because the default will be for the
macro to not be defined. The user has to define
_RWSTD_NO_FWD_DECLARATIONS to get the declarations from the correct and
normal place [windows.h]. It seems to me that the macro should be
_RWSTD_NO_INCLUDE_WINDOWS_H or something similar.

Travis


>-----Original Message-----
>From: Farid Zaripov [mailto:Farid_Zaripov@epam.com]=20
>Sent: Friday, August 10, 2007 6:58 AM
>To: stdcxx-dev@incubator.apache.org
>Subject: missprint in include/rw/_mutex.h ?
>
>  Below is a part of the include/rw/_mutex.h file, line 116:
>
>-----------=20
>#  ifdef _RWSTD_NO_FWD_DECLARATIONS
>=20
>#    include <windows.h>
>#    define _RWSTD_MUTEX_T _RTL_CRITICAL_SECTION
>=20
>#  else   // if defined (_RWSTD_NO_FWD_DECLARATIONS)
>=20
>   // avoid #including this header (MFC doesn't like it)
>   // #  include <windows.h>
>-----------=20
>
>  Perhaps there in the first line should be #ifndef instead of #ifdef ?
>=20
>Farid.
>