Time does not stand still. VS 2015 is fine. Too soon for something newer
ATM.
On Sat, Nov 11, 2017 at 6:48 PM, Juan Abadía <juan.abadia@xxxxxxxxx> wrote:
In my opinion there is no point in still using vs2013 or older.
Juan
On 11 Nov 2017, at 19:36, Garrett D'Amore <garrett@xxxxxxxxxx> wrote:apps.)
(Ignore this message if you don’t use Visual Studio to build Windows
newer for the new nng library. (Today it works with older revs, but I
I’m contemplating building in a requirement for VIsual Studio 2013 or
don’t test anything too old.)
(incomplete though), so that I can start using things like <stdbool.h> and
The motivation here is that the 2013 edition introduced C99 support
<stdint.h>
What about with nng? How disruptive would it be for you if nng were to
Do you use support for older versions of Visual Studio with nanomsg?
require Visual Studio 2013 or newer? What about 2015 or newer? What if
nng permitted using older compilers to build *against* nng, provided that
nng itself were compiled with a sufficiently modern edition of VS?
- Garrett
