Article View: net.std
Article #10Automated Standardization
From: sa
Date: Wed, 29 Feb 1984 19:16
Date: Wed, 29 Feb 1984 19:16
32 lines
1873 bytes
1873 bytes
< AUTOMATED STANDARDS >
I am in the process of designing an automated standardizing
system. Its function, given a standard, is to force a non-standard
system into the form of the given standard. The types of entities
suitable for standardizing include:
1. Lexical Entities
The relative positioning of any lexicographic primitive to
another.
2. Data Base Coupling
The relative strength or weakness of data transmission channels
(parameters, functional returns, condition flags, etc.)
3. Commenting
Rules for commenting as the apply to to structure of the code
and train of thought.
4. Semantic Entities
Code should reflect meaning. For example, code pertinent to
the initialization of 'while' loops should be placed 'near' the
'while' loop beginning.
I am looking for ADDITIONAL CATEGORIES and category-
specific SUGGESTIONS. For contributors, I will make available the
finished product; for the net, I will post summaries subject to
debate and refinement.
Stephen Amerige
... !harpo!utah-cs!beesvax!byucsa!sa
Or: C-2212 Helaman
Provo, Utah 84604
(or any other path that is good for you).
Technical Details
Message-ID:
<124@byucsa.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!watmath!clyde!floyd!harpo!utah-cs!beesvax!byucsa!saShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 beta 3/9/83; site byucsa.UUCP Path: arc1-ca.pugleaf.net!utzoo!watmath!clyde!floyd!harpo!utah-cs!beesvax!byucsa!sa From: sa@byucsa.UUCP Newsgroups: net.std Subject: Automated Standardization Message-ID: <124@byucsa.UUCP> Date: Wed, 29-Feb-84 14:16:07 EST Article-I.D.: byucsa.124 Posted: Wed Feb 29 14:16:07 1984 Date-Received: Fri, 2-Mar-84 06:26:02 EST Organization: ...!harpo!utah-cs!beesvax!byucsa!sa Lines: 33