Hello Carsten, Wednesday, December 16, 2009, 11:57:23 PM, you wrote:
Just one point. >> 2) it bloats the code, in some case substantially, and obscures >> the "real" code flow CB> The real code flow ends in nothing. There are embedded CPU's that have CB> no problem with writing to zero. They just do it. So this is really nice CB> to search errors. Good luck. here I meant the code flow for someone who is reading the source, not the CPU execution path. Actually, I think a common emalloc() function that (in the unlikely event of malloc failure) prints an error message and exits the app is a better choice than sticking checks everywhere. -- WBR, Igor mailto:skochin...@mail.ru _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
