Roger R. Baldwin

We don’t have enough information about this author to calculate their statistics. If you think this is an error let us know.
Learn More
It is not necessary to use a backward-directed GO TO in FORTRAN. In othe r words, if a FORTRAN program exists which contains backward-directed GO TOs, the n other FORTRAN program(s) exist with (1) the same functionality as the origina l program and (2) no backward-directed GO TOs. 2. Argumen t Bohm and Jacopini [Bohm66J have shown that the control(More)
Fred Brooks summarized what he has learned about Software Engineering since the publication of "The Mythical Man-Month" (MMM): • The advantage of "incremental build". (Under incremental build, a rudimentary version of the software is built as soon as possible. The earliest version consists of a driver and stubs. Then function is added incrementally.) The(More)
(2) The development of a Jackson-designed progra m is easy to interrupt . This follows from the fac t that the design process is divided into fou r steps, each with well-defined work products . A t the end of each step it is easy to do something else for an hour or a week . (This feature wa s of great personal importance . In the sixteen month period under(More)
COBOL practitioners know that misplaced periods are a common source of program bugs. One reason for the trouble is the inconsistent use of the period required by the COBOL standard [ANSI74]. Sometimes the period is absolutely necessary, e.g. to terminate an IF statement, and sometimes it is forbidden, e.g. within an IF statement. More generally, the period(More)
In my view Neta Amit's [Amit 84a] is the best art ic le to date on Deeply Nested IF-THEN-ELSEs. In particular, I have successfully applied one of his "restricted problem" solutions, Figure 4 in [Amit 84a], to an ll-deep IF nest in a production PL/I program. However, despite my admiration for his work, I do find room for improvement. More specifically, his(More)
  • 1