search

lilijreey / bwapi

Automatically exported from code.google.com/p/bwapi
0 stars 0 forks source link

Do something about Visual C++ 2010 #408

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
As you know the released library on the Downloads section does not work on 
Visual C++ 2010 due to version incompatibility.

Releasing library for Visual C++ 2010, allows the user to use the latest 
feature of C++ included within Visual C++ 2010 (I am just asking for the 
XXX.lib file and not the whole development environement).

Original issue reported on code.google.com by aurelien...@gmail.com on 28 Sep 2011 at 3:11

GoogleCodeExporter commented 9 years ago 
Before next release, let's maybe do something about VC++ 2010 since there have 
been issues in the past about it, and now it's 2011, going to be 2012 in a few 
months, we should probably consider some kind of compatibility mode or 
switching to VC++ 2010 Express ourselves.

Thoughts?

Original comment by AHeinerm on 28 Sep 2011 at 9:14

GoogleCodeExporter commented 9 years ago 
I think that about the following approach:

I think the most simple would be to switch to VC++ 2010 and to recommand user 
to switch to VC++ 2010 as well. This way, it will help the global project in 
general to keep up to the actual compiler with mean better support for newer 
C++ standard et better compiler.

If do not quite agree of supporting two different version of VC++ since it 
would mean more incompatibility problem. For example, new C++ feature not 
supported in previous version etc... This can also be avoided by setting some 
coding rule to not use the recent C++ standard.

If you do still want to support both version, you should have some clear 
directive on how long do you plan to support the old version. This way, it 
would help the user to switch themselves to the most recent VC++ IDE, for a 
better transition.

I also notice that you do not tag the source code when you do a release. You 
may upgrade your release procedure. If you do a tag of the trunk for each 
release you do, all developer can be sure that, if they compile the latest tag 
of bwapi they will have the version matching the release one (if support for 
one version is not provided anymore).

Original comment by aurelien...@gmail.com on 30 Sep 2011 at 5:59

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 3 Dec 2011 at 4:00

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 12 Jan 2012 at 5:11