- 2021.01.04 14:55 "Re: [Tiff] Motions related to C99 use in libtiff", by Edward Lam
- 2021.01.04 18:43 "Re: [Tiff] Motions related to C99 use in libtiff", by Greg Troxel
- 2021.01.05 17:01 "Re: [Tiff] Motions related to C99 use in libtiff", by Jeff Breidenbach
- 2021.01.05 20:29 "Re: [Tiff] Motions related to C99 use in libtiff", by Kurt Schwehr
- 2021.01.05 20:46 "Re: [Tiff] Motions related to C99 use in libtiff", by Kemp Watson
-
2021.01.06 04:45 "Re: [Tiff] Motions related to C99 use in libtiff", by William Bader
- 2021.01.06 10:40 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
- 2021.01.06 14:15 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn
-
2021.01.10 12:12 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
- 2021.01.10 14:54 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn
- 2021.01.10 16:27 "Re: [Tiff] Motions related to C99 use in libtiff", by Roger Leigh
- 2021.01.15 15:58 "Re: [Tiff] Motions related to C99 use in libtiff", by Even Rouault
2021.01.06 16:44 "Re: [Tiff] Motions related to C99 use in libtiff", by Bob Friesenhahn
libtiff is a C library. That would be broken C++ code and frankly none of our concern. At some point we have to draw a line and not accept responsibility for all the code in the universe.
It is not broken C++ code to use interface types as part of its implementation. C++ itself is "broken" in that the definition of a class must expose the complete interface (including "private" parts). It takes extra work to develop C++ interface code which entirely hides the implementation.
I was only answering a question which was asked.
I will gently remind that most of us contributing time to the project do so as volunteers. That certainly applies to me.
Bob
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt