Evan Layton wrote: > > Here is the functional/design spec for the BE error and observability > project. > > It's a first version and does include some design elements for what > will eventually become the error handling and logging service for the > Caiman Unified Design project. However this project is not intended to > provide that error handling and logging but just the beginnings of it > and the ability to mesh easily with it. > > I would like to get any comments by the end of the day on Friday (8/21). > > Thanks! > -evan > > ------------------------------------------------------------------------ > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss Evan,
I think this will go a long way in making BE more user friendly. I have only 1 suggestions. Instead of passing strings in the err_info_str struct I think it would be better, where possible, to pass a unique error code (integer) that could be defined in a single "BE" header file. This way the text can be modified in one place. I realize the error text returned from the underlying system calls can not be easily maintained in this way, but if it is possible for at least the BE specific message text I think it would be more easily maintainable. Joe
