>>> +#define RV_OK 0 >>> +#define RV_NO_VALUE -1 >>> +#define RV_NO_MEM -2 >>> +#define RV_WRONG_VALUE -3 >>> +#define RV_UNKNOWN_ERR -4 >> Why not #include <errno.h> and use ENOMEM, EINVAL, etc? Why reinvent >> the wheel? >> > I don't see any error code for empty value, for instance. So, I don't > like the idea of shoehorning a POSIX error code for my specific error. I > see the problem with the RV_NO_MEM case, however there's only one error > code matching a POSIX error code.
I still think the POSIX error codes are the way to go, but it's hardly worth arguing over. Your way works fine. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ TrouSerS-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-tech
