> -Original Message-
> From: Martin Sebor [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 05, 2007 7:02 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: [PING] Re: svn commit: r541672 -
> /incubator/stdcxx/trunk/include/rw/_config-msvc.h
>
> > I
Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Monday, June 04, 2007 9:36 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: [PING] Re: svn commit: r541672 -
/incubator/stdcxx/trunk/include/rw/_config-msvc.h
What I see, is that we
> -Original Message-
> From: Martin Sebor [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 04, 2007 9:36 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: [PING] Re: svn commit: r541672 -
> /incubator/stdcxx/trunk/include/rw/_config-msvc.h
>
> > What I s
Farid Zaripov wrote:
Farid, do you agree that this is the way to go? If you do, do
you plan to move the Intel C++ specific code to the
_config-icc.h header? (Just making sure this doesn't slip
through the cracks.)
I need to inspect what the macros from _config_msvc.h are Intel C++
compiler
Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 8:39 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: svn commit: r541672 -
/incubator/stdcxx/trunk/include/rw/_config-msvc.h
Well, I guess we need to decide if it
> -Original Message-
> From: Martin Sebor [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 29, 2007 8:39 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: svn commit: r541672 -
> /incubator/stdcxx/trunk/include/rw/_config-msvc.h
>
> Well, I guess we need
Farid Zaripov wrote:
I wonder if it wouldn't be cleaner to move all the Intel C++
specific code out of _config-msvc.h and into _config-icc.h
and make sure we #include the former only for MSVC and the
latter only for Intel C++. One of the goals of separating all
the compiler-specific hacks and
> Farid, do you agree that this is the way to go? If you do, do
> you plan to move the Intel C++ specific code to the
> _config-icc.h header? (Just making sure this doesn't slip
> through the cracks.)
I need to inspect what the macros from _config_msvc.h are Intel C++
compiler specific (exce
> I wonder if it wouldn't be cleaner to move all the Intel C++
> specific code out of _config-msvc.h and into _config-icc.h
> and make sure we #include the former only for MSVC and the
> latter only for Intel C++. One of the goals of separating all
> the compiler-specific hacks and overrides wa
Farid, do you agree that this is the way to go? If you do,
do you plan to move the Intel C++ specific code to the
_config-icc.h header? (Just making sure this doesn't slip
through the cracks.)
Martin
Martin Sebor wrote:
[EMAIL PROTECTED] wrote:
Author: faridz
Date: Fri May 25 07:41:40 2007
Ne
[EMAIL PROTECTED] wrote:
Author: faridz
Date: Fri May 25 07:41:40 2007
New Revision: 541672
URL: http://svn.apache.org/viewvc?view=rev&rev=541672
Log:
2007-05-25 Farid Zaripov <[EMAIL PROTECTED]>
* _config-msvc.h: MSVC specific #pragma's decorated with #ifndef
_INTEL_COMPILER;
11 matches
Mail list logo
