diff options
| author | Julien Nabet <serval2412@yahoo.fr> | 2012-05-02 11:07:29 +0200 |
|---|---|---|
| committer | Julien Nabet <serval2412@yahoo.fr> | 2012-05-02 11:07:42 +0200 |
| commit | 7b84d0fcd2d6eeb9ae1da836c115213c4197acd1 (patch) | |
| tree | b640f2216c620478fdf90763f2dcf283fa7a175c | |
| parent | 602f251d6c5f1f5551cdeb4c70abe0c49834d2c7 (diff) | |
Fix typo
Change-Id: I3b01defa109b87c5c7f4c5b4e44e846de7d7ddf1
| -rw-r--r-- | unusedcode.README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/unusedcode.README b/unusedcode.README index c721d6237327..7b867dfa8661 100644 --- a/unusedcode.README +++ b/unusedcode.README @@ -26,7 +26,7 @@ d) gcc will only emit code for inlines if those inlines are used, so compile time after an attempt at removal. i.e. generally the inline method can go as well because nothing calls it either, a double win. e) if a constructor is listed as unused, and it's the *only* ctor in the class, - then no object of that class can be construsted, so the whole thing is + then no object of that class can be constructed, so the whole thing is unused, which can lead to a whole cascade of tricky but logical fallout. f) if a destructor is listed as unused, and a constructor isn't, then there's a leak somewhere, and the destructor most likely *should* be called. |