c
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| c [2015/12/31 02:29] – [Have it reviewed] admin | c [2016/01/03 23:44] – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====Writing | + | ====== Decent |
| I've been writing c for over 30 years, but it can still be a nightmare - the problems are well documented elsewhere. The discipline of writing device drivers for Linux/ | I've been writing c for over 30 years, but it can still be a nightmare - the problems are well documented elsewhere. The discipline of writing device drivers for Linux/ | ||
| ====Single return point==== | ====Single return point==== | ||
| - | Every routine should have a single return point. All possible execution paths go through this point and therefore have the chance to have resources released. The main thing, of course, is to free resources that are no longer needed eg memory that has been malloc()' | + | Every routine should have a single return point. All possible execution paths go through this point and therefore have the chance to have resources released. The main thing, of course, is to free resources that are no longer needed eg memory that has been malloc()' |
| ====Error responses should be close to the failing statement==== | ====Error responses should be close to the failing statement==== | ||
| and not dangling at the end of some huge }}}} block ten pages away!!! Deal with it _now_, to hell with making the Happy Path clearer - the Happy Path is easy, it's the errors that make the thing beastly. | and not dangling at the end of some huge }}}} block ten pages away!!! Deal with it _now_, to hell with making the Happy Path clearer - the Happy Path is easy, it's the errors that make the thing beastly. | ||
| Line 12: | Line 12: | ||
| Do it even when it looks stupidly simple - later, when the routine is made more elaborate, then the logic is in place and you will remember to cleanup: | Do it even when it looks stupidly simple - later, when the routine is made more elaborate, then the logic is in place and you will remember to cleanup: | ||
| - | < | + | < |
| /* @return 0 if file is foobarable. Otherwise 1. | /* @return 0 if file is foobarable. Otherwise 1. | ||
| */ | */ | ||
c.txt · Last modified: 2020/10/17 03:05 by 114.119.151.1