Re: [gdal-dev] Starting a discussion on style and coding guidelines

2016-05-07 Thread Kurt Schwehr
Mateusz, Thanks for calling out the confusion! Are meaning to say that my proposal is vague? I rephrased the status to be more clear that the C++11/14 focus is the GDAL community (AKA the majority of this threa

Re: [gdal-dev] how to write multi-IFD TIFF files ?

2016-05-07 Thread Even Rouault
Le samedi 07 mai 2016 23:57:18, fred p a écrit : > Hello, > I am looking for a way to write multi-IFD TIFF files with GDAL (each IFD > being JPEG or LZW compressed), for example with gdal_translate or (better > if possible) the Python API but without any success. > Is it possible anyway ? Hi, No

Re: [gdal-dev] Starting a discussion on style and coding guidelines

2016-05-07 Thread Tim Keitt
On Fri, May 6, 2016 at 2:47 PM, Kurt Schwehr wrote: > For stack ranking, see the "alternatives" section of this (and I did not > include my preferred std::vector solution in the list): That seems like a reasonable solution. The function/method call interface is where I would begin substituting

Re: [gdal-dev] Starting a discussion on style and coding guidelines

2016-05-07 Thread Tim Keitt
http://www.keittlab.org/ On Fri, May 6, 2016 at 2:47 PM, Mateusz Loskot wrote: > On 6 May 2016 at 21:55, Kurt Schwehr wrote: > > My belief is that for this particular proposal, we should not have the > > C++11/14 discussion unless the best overall solution requires a newer > > version of C++.

[gdal-dev] how to write multi-IFD TIFF files ?

2016-05-07 Thread fred p
Hello, I am looking for a way to write multi-IFD TIFF files with GDAL (each IFD being JPEG or LZW compressed), for example with gdal_translate or (better if possible) the Python API but without any success. Is it possible anyway ? Thanks for your help ! _

Re: [gdal-dev] Minimum supported C and C++ standards

2016-05-07 Thread Andrew Bell
On Sat, May 7, 2016 at 2:00 PM, David Strip wrote: > On 5/7/2016 11:10 AM, Kurt Schwehr wrote: > > This is cart before the horse but... as fast as I can so expect typos. > Now just think of a ~1K long function or method with tons of instances and > lots of places to bailout successfully or as f

Re: [gdal-dev] Minimum supported C and C++ standards

2016-05-07 Thread David Strip
On 5/7/2016 11:10 AM, Kurt Schwehr wrote: This is why starting with zero features and working our way up with a white list gives examples of correct usage.  It looks like a lot of GDAL development happens by copy-paste-tweak, so good examples are key.  An

Re: [gdal-dev] Minimum supported C and C++ standards

2016-05-07 Thread Kurt Schwehr
This is example demonstrates that we are in-general fighting hard against C++... up-hill both ways in a blizzard. :) This is why starting with zero features and working our way up with a white list gives examples of correct usage. It looks like a lot of GDAL development happens by copy-paste-twe

Re: [gdal-dev] Minimum supported C and C++ standards

2016-05-07 Thread David Strip
Even raises an important point about adopting the latest C++ standards. This point actually applies to C++ in general as well. In particular, C++ can be used to write some very powerful but tremendously opaque code. This problem is amplified by the inscrutable error messa

Re: [gdal-dev] Minimum supported C and C++ standards

2016-05-07 Thread Even Rouault
Le vendredi 06 mai 2016 23:07:26, Kurt Schwehr a écrit : > There has been lively discussion on if/when GDAL moves to require compilers > with newer C and C++ standard versions. This email is meant to fork the > this discussion away from the local stack + memset -> std::vector > discussion. I'm tr