Effectiveness and efficiency of software development can be greatly increased by writing modularized code using informal (styles) and formal (standards) work approaches. Software development is about connecting pieces into a coherent whole. Thus consistent work approaches provide a structure that allows individuals and teams to minimize the time and thought put into making these connections. These investments in structure return even more benefits in the maintenance phase when old code has to be examined by new programmers, or after time has passed. We present some examples of coding style for Avenue: a simplified form of Hungarian notation (notationHungarian, stringCustomerName, etc.), …
continued below
Publisher Info:
Sandia National Labs., Albuquerque, NM (United States)
Place of Publication:
Albuquerque, New Mexico
Provided By
UNT Libraries Government Documents Department
Serving as both a federal and a state depository library, the UNT Libraries Government Documents Department maintains millions of items in a variety of formats. The department is a member of the FDLP Content Partnerships Program and an Affiliated Archive of the National Archives.
Descriptive information to help identify this article.
Follow the links below to find similar items on the Digital Library.
Description
Effectiveness and efficiency of software development can be greatly increased by writing modularized code using informal (styles) and formal (standards) work approaches. Software development is about connecting pieces into a coherent whole. Thus consistent work approaches provide a structure that allows individuals and teams to minimize the time and thought put into making these connections. These investments in structure return even more benefits in the maintenance phase when old code has to be examined by new programmers, or after time has passed. We present some examples of coding style for Avenue: a simplified form of Hungarian notation (notationHungarian, stringCustomerName, etc.), script naming prefixes and suffixes, and options in script headers. We demonstrate several modular, object-like utility scripts that can be used alone or combined into other utilities. These include developer tools such as a System.Echo substitute for Windows, a Window inspector, and a script for detecting and dealing with multiple display resolutions.
This article is part of the following collection of related materials.
Office of Scientific & Technical Information Technical Reports
Reports, articles and other documents harvested from the Office of Scientific and Technical Information.
Office of Scientific and Technical Information (OSTI) is the Department of Energy (DOE) office that collects, preserves, and disseminates DOE-sponsored research and development (R&D) results that are the outcomes of R&D projects or other funded activities at DOE labs and facilities nationwide and grantees at universities and other institutions.
Ganter, J.Arc View/Avenue: Coding styles and utility scripts for efficient development,
article,
May 7, 1996;
Albuquerque, New Mexico.
(https://digital.library.unt.edu/ark:/67531/metadc666653/:
accessed April 25, 2024),
University of North Texas Libraries, UNT Digital Library, https://digital.library.unt.edu;
crediting UNT Libraries Government Documents Department.