Seldom does a computer program start at the first line of code and sequentially process each line until the last line of code. Rather, the flow often takes "detours," but still arriving at the desired location. This is as it should be, much like the driver of a car does not always travel in a straight line to his destination. Decisions are made along the way as to the direction that must be followed. Experience tells us that maintaining a large program is best done by constructing small, manageable pieces called functions and assembling these pieces into a greater whole. It amounts to a "divide and conquer" approach to problem solving. This requires a sound understanding of storage classes and scope rules. Response and or thoughts?