Flowcharting with D-charts

A D-Chart is a style of flowchart using control symbols highly appropriate to modern structured programming languages. The intent of a D-Chart is to provide a clear and concise one-for-one mapping of control symbols to high-level language constructs for purposes of design and documentation. The notation lends itself to both high-level and code-level algorithmic description. The various issues that may arise when representing, in D-Chart style, algorithms expressed in the more popular high-level languages are addressed. In particular, the peculiarities of mapping control constructs for Ada, PASCAL, FORTRAN 77, C, PL/I, Jovial J73, HAL/S, and Algol are discussed

Development of a KSC test and flight engineering oriented computer language, Phase 1

Ten, primarily test oriented, computer languages reviewed during the phase 1 study effort are described. Fifty characteristics of ATOLL, ATLAS, and CLASP are compared. Unique characteristics of the other languages, including deficiencies, problems, safeguards, and checking provisions are identified. Programming aids related to these languages are reported, and the conclusions resulting from this phase of the study are discussed. A glossary and bibliography are included. For the reports on phase 2 of the study, see N71-35027 and N71-35029

Editorial : Poverty and mobility in England, 1600–1850

Within these pages you will find a ‘jovial crew’: rogues and vagabonds, the ‘mad’ and insane, gypsies, peddlers, poets, playwrights, pilgrims, rioters, convicts, constables, thieves, beggars, landed gentlemen, magistrates, and historians. When parliamentarians and projectors set out to proscribe mobility and legislate poverty in early modernity, a list of untrustworthy trades and professions not at all unlike this one frequently found its way into print and the statute book. The punishment for crimes of vagrancy could be severe, but thankfully ‘historians’ were not counted among the undeserving and mobile, nor would you find magistrates and landed gentlemen taken up, imprisoned, and whipped for a crime of movement. However, all three groups may well deserve some of John Locke's brand of draconian ‘improvement’; historians in particular have taken little account of the lived experiences of the mobile poor until relatively recently. Once we finally took a hard look at our inherited, literature-driven typologies of ‘rogues’ and ‘beggars’, they disappeared in ‘a storm of dust and lies.’ However, the literary, visualised vagabond still has much to tell us, and interdisciplinary approaches to vagrancy in the past have emerged as the strongest method yet of reconstructing the character, history, and cultural perception of the mobile poor. These are methods which the articles in this collection use to full effect

An Ada programming support environment

The toolset of an Ada Programming Support Environment (APSE) being developed at North American Aircraft Operations (NAAO) of Rockwell International, is described. The APSE is resident on three different hosts and must support developments for the hosts and for embedded targets. Tools and developed software must be freely portable between the hosts. The toolset includes the usual editors, compilers, linkers, debuggers, configuration magnagers, and documentation tools. Generally, these are being supplied by the host computer vendors. Other tools, for example, pretty printer, cross referencer, compilation order tool, and management tools were obtained from public-domain sources, are implemented in Ada and are being ported to the hosts. Several tools being implemented in-house are of interest, these include an Ada Design Language processor based on compilable Ada. A Standalone Test Environment Generator facilitates test tool construction and partially automates unit level testing. A Code Auditor/Static Analyzer permits the Ada programs to be evaluated against measures of quality. An Ada Comment Box Generator partially automates generation of header comment boxes

A study of systems implementation languages for the POCCNET system

The results are presented of a study of systems implementation languages for the Payload Operations Control Center Network (POCCNET). Criteria are developed for evaluating the languages, and fifteen existing languages are evaluated on the basis of these criteria