AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

1994.02.10 19:32 "LibTIFF working on MS-Windows 3.1.", by Soren Pingel Dalsgaard
1994.02.11 09:39 "Re: LibTIFF working on MS-Windows 3.1.", by Bjorn P. Brox
1994.02.11 01:09 "Re: LibTIFF working on MS-Windows 3.1.", by Richard Minner
1994.02.11 14:40 "Re: LibTIFF working on MS-Windows 3.1.", by Jie Yao
1994.02.11 01:16 "Re: LibTIFF working on MS-Windows 3.1.", by Richard Minner
1994.02.11 10:17 "Re: LIBTIFFW working on MS-Windows 3.1.", by Niles Ritter
1994.02.14 11:03 "Error/warning handlers in libtiff", by Erik Corry
1994.02.16 22:38 "Re: Error/warning handlers in libtiff", by Sam Leffler
1994.02.11 18:27 "Re: LibTIFF working on MS-Windows 3.1.", by Francois Gauthier
1994.02.11 21:29 "Re: LibTIFF working on MS-Windows 3.1.", by Sam Leffler

1994.02.11 01:16 "Re: LibTIFF working on MS-Windows 3.1.", by Richard Minner

more correct way for libtiff to do, I think, is to have these routines set a variable like TIFFerrno, The library should never report error messages on its own way. If it fails, return a failure. The application then check the error number, and report in what ever way it likes.

Not quite, because the messages are not simply "error 2: you lose" but rather contain very useful details of the circumstances of the failure. The current callback scheme is by far the preferred method for reporting diagnostics.

Currently, in the windows 3.1, we have to set error/warning handler anyway. I think to have them do nothing would be a good idea.

They should do nothing only #ifdef _WINDOWS; on other systems the defaults are useful.

--
Richard Minner rtm@island.com {uunet,sun,well}!island!rtm
Island Graphics Corporation Sacramento, CA (916) 736-1323