1"use strict";(self.webpackChunkada_lang_io=self.webpackChunkada_lang_io||[]).push([["5037"],{76020(e,t,n){n.r(t),n.d(t,{metadata:()=>s,default:()=>u,frontMatter:()=>r,contentTitle:()=>o,toc:()=>l,assets:()=>c});var s=JSON.parse('{"id":"style-guide/s5/s5","title":"5. Programming Practices","description":"Software is always subject to change. The need for this change,","source":"@site/docs/style-guide/s5/s5.mdx","sourceDirName":"style-guide/s5","slug":"/style-guide/s5/","permalink":"/docs/style-guide/s5/","draft":false,"unlisted":false,"tags":[],"version":"current","sidebarPosition":5,"frontMatter":{"title":"5. Programming Practices","sidebar_position":5},"sidebar":"styleGuideSidebar","previous":{"title":"4.4 Summary","permalink":"/docs/style-guide/s4/04"},"next":{"title":"5.1 Optional Parts of the Syntax","permalink":"/docs/style-guide/s5/01"}}'),a=n(74848),i=n(28453);let r={title:"5. Programming Practices",sidebar_position:5},o,c={},l=[];function d(e){let t={em:"em",p:"p",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsxs)(t.p,{children:["Software is always subject to change. The need for this change,\neuphemistically known as ",(0,a.jsx)(t.em,{children:'"maintenance"'})," arises from a variety of\nsources. Errors need to be corrected as they are discovered. System\nfunctionality may need to be enhanced in planned or unplanned ways.\nInevitably, the requirements change over the lifetime of the system,\nforcing continual system evolution. Often, these modifications are\nconducted long after the software was originally written, usually by\nsomeone other than the original author."]}),"\n",(0,a.jsx)(t.p,{children:"Easy and successful modification requires that the software be readable,\nunderstandable, and structured according to accepted practice. If a\nsoftware component cannot be easily understood by a programmer who is\nfamiliar with its intended function, that software component is not\nmaintainable. Techniques that make code readable and comprehensible\nenhance its maintainability. Previous chapters presented techniques such\nas consistent use of naming conventions, clear and well-organized\ncommentary, and proper modularization. This chapter presents consistent\nand logical use of language features."}),"\n",(0,a.jsx)(t.p,{children:"Correctness is one aspect of reliability. While style guidelines cannot\nenforce the use of correct algorithms, they can suggest the use of\ntechniques and language features known to reduce the number or\nlikelihood of failures. Such techniques include program construction\nmethods that reduce the likelihood of errors or that improve program\npredictability by defining behavior in the presence of errors."})]})}function u(e={}){let{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,a.jsx)(t,{...e,children:(0,a.jsx)(d,{...e})}):d(e)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.