-
2004.09.15 13:46 "Re: [Tiff] Calltype support", by Frank Warmerdam
-
2004.09.15 15:02 "Re: [Tiff] Calltype support", by Bob Friesenhahn
-
2004.09.15 15:25 "Re: [Tiff] Calltype support", by Frank Warmerdam
- 2004.09.15 15:38 "Re: [Tiff] Calltype support", by Bob Friesenhahn
-
2004.09.15 15:25 "Re: [Tiff] Calltype support", by Frank Warmerdam
-
2004.09.15 15:02 "Re: [Tiff] Calltype support", by Bob Friesenhahn
2004.09.15 13:46 "Re: [Tiff] Calltype support", by Frank Warmerdam
This works perfectly, but has a great disadvantage: Migrating to a new version of the LibTiff is painful because we have to do the same work again.
Have you ever thought about adding calltype support, like the JPEGlib does? I think the readability of the code does not decrease. Or are there other (better?) ways to add calltype support?
Martin,
I would agree that wrapping all the public definitions in appropriate macros is desirable and I do this on various other projects. Please submit a bug with the request.
However, isn't there a way to direct the compiler to use a particular calling convention that would avoid all this?
Best regards,
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent