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]

Macintosh naming conventions

macro routines

    alternatives for [See routines, macro]

     limitations on

     multiple statements in

     naming 2nd

     parentheses with

magazines on programming magic variables, avoiding 2nd 3rd

maintenance     comments requiring     design goal for

     error-prone routines, prioritizing for

     fixing defects, problems from

     maintainability defined     readability benefit for

     structures for reducing major construction practices checklistmanaging construction    code ownership attitudes [See construction, managing]

     complexity

     good coding, encouraging

     inspections, management role in

     key points     managers     measurements     programmers, treatment of

     readability standard     resources on     reviewing all code

     rewarding good practices

     schedules, estimating

     signing off on code

     standards, authority to set     standards, IEEE 2nd

     two-person teams

markers, defects from matrices

mature technology environments

maximum normal configurations maze recursion example

McCabe's complexity metric 2nd measure twice, cut once

measurement

     advantages of

     arguing against

     goals for

     outlier identification

     resources for

     side effects of

     table of useful types of

memory

     allocation, error detection for

     corruption by pointers

     fillers

     initializing working     paging operation performance impact

     pointers, corruption by     tools for mentoring

merge tools

metaphors, software

     accreting a system     algorithmic use of 2nd

     building metaphor     building vs. buying components     combining     computer-centric vs. data-centric views

     customization

     discoveries based on

     earth centric vs. sun centric views

     examples of     farming     growing a system     heuristic use of

     importance of     incremental development     key points for

     modeling use for

     overextension of

     oyster farming

     pendulum example     power of

     readability

     relative merits of 2nd     simple vs. complex structures

     size of projects

     throwing one away     toolbox approach

     using     writing code example

methodologies [See also approaches to development]

methods

metrics reporters

minimum normal configurations

mission-critical systems

mixed-language environments

mixins

mock objects

modeling, metaphors as

moderator role in inspections

modularity

     design goal of

     global variables, damage from modules, coupling considerations

multiple inheritance multiple returns from routines multiple-file string search capability