of Windows devs. We don't get a whole
> lot of C++11 for that upgrade though, and what we get isn't actually
> standards compliant.
>
>
>
> From: Jens Geyer
> To: "dev@thrift.apache.org" ,
> Date: 03/20/2015 03:12 AM
> Subject:AW: AW: [
le
lot of C++11 for that upgrade though, and what we get isn't actually
standards compliant.
From: Jens Geyer
To: "dev@thrift.apache.org" ,
Date: 03/20/2015 03:12 AM
Subject: AW: AW: [DISCUSS] let's switch to C++11 (was Re: [jira]
[Commented] (THRIFT-3043) g
Forget it ... maybe I should read everything before I start to answer. It was
of course 2013
Von: Jens Geyer
Gesendet: 20.03.2015 09:09
An: dev@thrift.apache.org
Betreff: AW: AW: [DISCUSS] let's switch to C++11 (was Re: [jira] [Commented]
(THRIFT-304
I compiled the compiler with Visual Studio and had no problems?
Von: Ben Craig
Gesendet: 19.03.2015 17:46
An: dev@thrift.apache.org
Cc: Jake Farrell
Betreff: Re: AW: [DISCUSS] let's switch to C++11 (was Re: [jira] [Commented]
(THRIFT-3043) go compiler generator use
Our company policy is to follow Microsoft with regard to supported Windows
versions, and we made good experiences with that approach.
That means to deprecate and mentally prepare to drop WinXP in near future. It
does not imply taking any action immediately, but as soon as WinXP
compatibility hi
+1
Von: Roger Meier
Gesendet: 18.03.2015 11:28
An: dev@thrift.apache.org
Betreff: Re: AW: [DISCUSS] let's switch to C++11 (was Re: [jira] [Commented]
(THRIFT-3043) go compiler generator uses non C++98 code)
I just installed latest mingw for Windows from
http://so
