Hi Øyvind,
>> The first thing i had to learn was, that it is verry uncommon in >> OpenOCD to check the result of malloc. > This is a known problem where we gladly accept patches to fix each > case. OK, then i will start to fix all the mallocs that are handled not correct yet and where i understand what to do if they fail. > You will see by digging into the mailing list that we, the > maintainers, are always very interested in cleaning up the code and > that we gladly accept patches. Fine, that's good to hear. I don't want to spend a lot of hours directly for /dev/null ;-). > If you have a patch that would allow others to run lint using an open > source tool, then that would be well received. It would be good to have a make target for that, so that users who have lint of there computers can run it. Something like "./configure --with-lint" But this comes later. > I do cleanup of this file in batches. This file is my responsiblity. > I'll fix this one for sure. OK, the i leave this out. > There may be some of these cases that are a matter of opinion or > taste, but generally following lint warnings/notes is a good idea. Ok. I know that some stuff can "taste not so good". So I only change things that i classify as important. Best Regards, Carsten _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
