> It doesn't strictly need to be. For example, the API I reference above > returns a 32-bit error code but also takes an optional value-return > parameter that provides domain-specific error information. These additional > parameters can also be stacked so nested failures can be communicated. This > ultimately provides a richer and more friendly error system for both the > developer as well as the end user of a tool using the API. The return codes > are for programmatic handling while the additional parameter is for > communicating errors to users.
Sounds like exceptions to me... I'd like to see som restrained and sensible use of C++ rather than reinventing analogue concepts in C in OpenOCD... -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
