Re: The Elements of Informix-4gl Style

Path: emory!wupost!usc!elroy.jpl.nasa.gov!ames!data.nas.nasa.gov!sun204.nas.nasa.gov!jcarter From: jcarter@sun204.nas.nasa.gov (John R. Carter Sr.) Newsgroups: comp.databases.informix Keywords: structure, coding Message-ID: <1992Mar16.194027.5391@nas.nasa.gov> Date: 16 Mar 92 19:40:27 GMT References: <10208@gollum.twg.com> Sender: news@nas.nasa.gov Reply-To: jcarter@sun204.nas.nasa.gov (John R. Carter Sr.) Organization: Numerical Aerodynamic Simulation Facility NASA Here's the convention we use. It is mostly adopted from code written by Arnie Banay of Boeing Computer Services Company in Seattle, WA (I have to give credit where credit is due): Conventions: t_ database tables. p_ are program records. If p_name and p_namex are two program records, then the one ending with x is a subset of the other one. This is in case not all the information in the p_name record needs to be displayed (example: pa_class & pa_classx). pa_ program array. po_ program array containing old database values for tracking changes by new input values n_ initial (null) program record. u_ update copy of program record. ua_ update copy of program array. sa_ screen array. LA_ array length (size). LW_ window length (size of screen array). ------------------------------------------------------------------------------ John R. Carter, Sr. Programmer/Analyst - Informix DBA Computer Sciences Corporation jcarter@nas.nasa.gov Numerical Aerodynamic Simulation 415/604-3662 NASA Ames Research Center, Moffett Field, CA 94035-1000 M/S 258-6 ------------------------------------------------------------------------------