Code Complete: A Practical Handbook of Software Construction, Second Edition

Index

[SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W]

Facade pattern

factorials

factoring [See also refactoring]

factory methods

     Factory Method pattern

     nested ifs refactoring example

     refactoring to

fan-in fan-out

farming metaphor fault tolerance feature-oriented integration

Fibonacci numbers

files

     ADTs, treating as     authorship records for

     C++ source file order     deleting multiple example     documenting     layout within

     naming 2nd

     routines in

final keyword, Java

finally statementsfixing defects    checking fixes [See defects in code, fixing]     checklist

     diagnosis confirmation     hurrying, impact of     initialization defects

     maintenance issues

     one change at a time rule

     reasoning for changes

     saving unfixed code     similar defects, looking for

     special cases

     symptoms, fixing instead of problems     understand first guideline

     unit tests for

flags     change, identifying areas of

     comments for bit-level meanings     enumerated types for

     gotos, rewriting with

     names for

     semantic coupling with

flexibility

     coupling criteria for

     defined

floating-point data types

    accuracy limitations [See data types, floating-point]

     BCD

     checklist

     costs of operations

     equality comparisons

     magnitudes, greatly different, operations with     rounding errors

     Visual Basic typesfor loops     advantages of

     formatting 2nd

     indexes

     purpose of foreach loops 2nd

formal inspections    author role [See collaboration, formal inspections; collaboration, inspections; defects in code, formal inspections for detecting]     benefit summary     blame game

     checklist

     CMM

     Code Complete example

     compared to other collaboration     defined     egos in     error checklists

     expected results from     fine-tuning     follow-up stage

     inspection meetings

     key points

     management role

     moderator role     overview stage

     performance appraisals from

     planning stage     preparation stage

     procedure for

     rate of code review     reports

     resources for     reviewer role

     reviews, compared to

     rework stage

     roles in

     scenarios approach

     scribe role

     stages of

     three-hour solutions meeting

formal technical reviews

formatting code

Fortran

functional cohesion

functional specification

functions    calculations converted to example [See classes, functions in]

     defined     disallowing     key point for

     naming conventions for 2nd

     private, overriding

     return values, setting     status as return value

     when to use Fundamental Theorem of Formatting