AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
September 2004

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2004.09.14 11:06 "Calltype support", by Martin Schramm
2004.09.15 13:46 "Re: Calltype support", by Frank Warmerdam
2004.09.15 15:02 "Re: Calltype support", by Bob Friesenhahn
2004.09.15 15:25 "Re: Calltype support", by Frank Warmerdam
2004.09.15 15:38 "Re: Calltype support", by Bob Friesenhahn
2004.09.16 17:54 "versioned symbols [Was: Calltype support]", by Jay Berkenbilt
2004.09.16 18:08 "Re: versioned symbols [Was: Calltype support]", by Thomas J Kacvinsky
2004.09.16 18:22 "Re: versioned symbols [Was: Calltype support]", by Jay Berkenbilt
2004.09.16 18:27 "Re: versioned symbols [Was: Calltype support]", by Thomas J Kacvinsky
2004.09.16 21:36 "Re: versioned symbols [Was: Calltype support]", by Andrey Kiselev
2004.09.16 22:36 "Re: versioned symbols [Was: Calltype support]", by Bob Friesenhahn
2004.09.19 15:52 "Re: versioned symbols [Was: Calltype support]", by Jay Berkenbilt
2004.09.19 19:34 "Re: versioned symbols [Was: Calltype support]", by Andrey Kiselev

2004.09.15 13:46 "Re: Calltype support", by Frank Warmerdam

Martin Schramm wrote:
> 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