Definitely no console output ever from library routines. (oiiotool is free to write to the console, however.)
Let's keep it a bool to indicate if there was an error. I think this is fine for now. If people crave actual error messages, we could use the existing IB error/geterror() (hmmm... geterror() is there, we should add a public error()) to set an error message in the result image's IB, so that an app could retrieve it. But we don't have to do this right now. On Jun 20, 2012, at 7:17 AM, Stefan Stavrev wrote: > Hi Chris, eh did not think about that. I will leave that aside for now though. > > 1. Should we print an error message on command line when over fails? We could > return int from over instead of bool, that will give us more info about the > error and we can print the appropriate message. This would be nice for both > the API user and the command line user. > > Let me know what you guys think. > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
