-
1999.06.04 03:45 "Re: Large File Support", by Frank Warmerdam
-
1999.06.07 13:00 "Re: Large File Support", by Rainer Wiesenfarth
- 1999.06.07 13:03 "Re: Large File Support", by Frank Warmerdam
- 1999.06.08 21:14 "Re: Large File Support", by Peter Smith
-
1999.06.07 13:00 "Re: Large File Support", by Rainer Wiesenfarth
- 1999.06.04 07:32 "Re: Large File Support", by Rob Tillaart
- 1999.06.04 18:35 "RE: Large File Support", by Bruce Forsberg
- 1999.06.10 09:48 "Re: Large File Support", by Klaus Bartz
- 1999.06.10 15:10 "Re: Large File Support", by Peter Smith
- 1999.06.14 11:16 "Re: Large File Support", by Martin Bailey
1999.06.10 13:21 "Re: Large File Support", by Chris Hanson
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 |