Re: [gdal-dev] GDAL testing

2015-10-17 Thread Mateusz Loskot
On 17 October 2015 at 06:14, Kurt Schwehr wrote: > What we have with autotest is super important. No doubt. > I've been trying to figure out how we take the first 17 > years of knowledge built up in GDAL and make keep going forward over the > next couple decades. A very interesting question. >

Re: [gdal-dev] Refactoring: class members clean-up

2015-10-17 Thread Mateusz Loskot
On 17 October 2015 at 12:54, Even Rouault wrote: > Le samedi 17 octobre 2015 00:25:45, Kurt Schwehr a écrit : >> I personally like foo_, but m_ is fine. I worry about unexpected side >> effects of changing member naming with private members. I don't think >> there will be any if everything build

Re: [gdal-dev] Refactoring: class members clean-up

2015-10-17 Thread Even Rouault
Le samedi 17 octobre 2015 00:25:45, Kurt Schwehr a écrit : > I personally like foo_, but m_ is fine. I worry about unexpected side > effects of changing member naming with private members. I don't think > there will be any if everything builds, but I still worry. There can be subtle effects inde

Re: [gdal-dev] Refactoring: class members clean-up

2015-10-17 Thread Mateusz Loskot
On 17 October 2015 at 00:25, Kurt Schwehr wrote: > I personally like foo_, but m_ is fine. I personally too, but we should stick to what has already been used in GDAL. > I worry about unexpected side > effects of changing member naming with private members. I don't suggest changing members visi

[gdal-dev] gdal_polygonize.py not running

2015-10-17 Thread Giorgio Ghiggini
Hi, I am using the GISInternals “release-1800-x64-gdal-1-11-1-mapserver-6-4-1” and I run the SDKShell.bat. Then I tried running the gdal_polygonize.py as is and I got the following message: - C:\GEC\