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
June 1999

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

1999.06.03 19:48 "Large File Support", by Bruce Forsberg
1999.06.04 03:45 "Re: Large File Support", by Frank Warmerdam
1999.06.04 07:32 "Re: Large File Support", by Rob Tillaart
1999.06.07 07:05 "Re: Large File Support", by Rainer Wiesenfarth
1999.06.08 21:14 "Re: Large File Support", by Peter Smith
1999.06.08 21:58 "Re: Large File Support", by Ed Grissom
1999.06.08 22:52 "Re: Large File Support", by Peter Smith
1999.06.09 01:27 "Re: Large File Support", by Martin Bailey
1999.06.09 06:50 "Re: Large File Support", by Owen Pearn
1999.06.09 14:33 "Re: Large File Support", by Martin Bailey
1999.06.09 08:07 "Re: Large File Support", by Rob Tillaart
1999.06.04 18:35 "Re: Large File Support", by Bruce Forsberg
1999.06.07 13:03 "Re: Large File Support", by Frank Warmerdam
1999.06.09 03:05 "Re: Large File Support", by <glen@lumisys.com>
1999.06.09 13:13 "Re: Large File Support", by Ed Grissom
1999.06.09 13:33 "Re: Large File Support", by Frank Warmerdam
1999.06.09 14:08 "Re: Large File Support", by Ed Grissom
1999.06.09 18:50 "Re: Large File Support", by Chris Barker
1999.06.09 18:41 "Large File Support", by Chris Barker
1999.06.10 13:21 "Re: Large File Support", by Chris Hanson
1999.06.10 13:52 "Re: Large File Support", by Frank Warmerdam
1999.06.10 14:37 "Re: Large File Support", by John Aldridge
1999.06.10 15:10 "Re: Large File Support", by Peter Smith
1999.06.10 16:56 "Re: Large File Support", by Chris Barker
1999.06.14 11:16 "Re: Large File Support", by Martin Bailey
1999.06.14 14:58 "Re: Large File Support", by Tom Lane
1999.06.14 15:30 "Re: Large File Support", by Eric Shapiro
1999.06.14 16:27 "Re: Large File Support", by Chris Barker
1999.06.14 15:51 "Re: Large File Support", by Martin Bailey
1999.06.09 15:52 "Re: Large File Support", by Ed Grissom
1999.06.10 09:48 "Re: Large File Support", by Klaus Bartz
1999.06.10 13:05 "Re: Large File Support", by Chris Hanson
1999.06.11 01:48 "Re: Large File Support", by <glen@lumisys.com>

1999.06.10 16:56 "Re: Large File Support", by Chris Barker

1. An "standard api" won't prevent you from being compatible with the
file
using a non-standard api. But it would be a godsend to the folks who
find
their current implementation deficient and need to plug in another
library.
I was merely suggesting that a "standard api" be defined alongside the
format,
and a reference implementaion made. You could then conform to one of
"TIFF64"
and "T64API", both, or neither.

But this is a big opportunity. With a cleverly designed API (I happen to
have
one here...) it would be possible to plug other formats in at the back
end,
leaving the api unchanged. We could then get a little order out of all
the
chaos.

Of course, a binding for each supported language would be required, but
I
don't think its as big a deal as you make it out to be. With nearly all
OSes
supporting shared libraries, these have to be (by their nature) somewhat
language independent.

As for being a "TIFF64" (or whatever) producer, you can be *that* with
any
libraries you care to write. I am suggesting the api bit for those who
care
to supply libraries (especially public domain ones).

I negelected to mention the important matter of a test suite (*very*
important)
which you have brought up. It should include a verifier.

Chris Hanson wrote:
> 
> barker@ilt.com wrote:
> > We need a real honest-to-goodness *standard* (without options) so we can
> > write good (and freely available) software. While standardizing the
> > format
> > it would also be an excellent idea to standardize the programming
> > interface
> > to read/write/verify/info-extract libraries.
> 
> I disagree.  I think it's extremely important that I be able to
> implement my code and API completely differently from yours and be able
> to call both of our libraries standards-conforming so long as we both
> pass a test suite.  I don't want to be prevented from claiming to be a
> compliant TI64 producer or consumer simply because I used C++ when the
> standard API was specified in C...
> 
> --
> Chris Hanson             | Disclaimer: I do not speak for Total
> Software Engineer        | Integration, Inc.  These are my opinions.
> Total Integration, Inc.  | Treat them as such, please.
> chanson@totalint.com     |

-- 
========================================================================
Barker's law: For every inaction, there is an equal and opposite excuse.

Check out Interlinear's web page at http://www.ilt.com
========================================================================