Q: Is a subroutine a sequence of program instructions that perform a specific task? ¶
A: Yes, and packaged as a unit.
Q: Were subroutines not explicitly separated from each other or from the main program? ¶
A: Yes, and indeed the source code of a subroutine could be interspersed with that of other subprograms.
Q: Is a subroutine assigned fixed memory locations? ¶
A: Yes, and it did not allow for recursive calls.
Q: Is a subroutine often coded so that it can be started several times and from several places during one execution of the program? ¶
A: Yes, and including from other subroutines, and then branch back to the next instruction after the call, once the subroutine's task is done.
Q: Are subroutines a powerful programming tool? ¶
A: Yes, and the syntax of many programming languages includes support for writing and using them.
Q: Are subroutines called predicates? ¶
A: Yes, since they primarily determine success or failure.
Q: Are subroutines key components in code maintenance? ¶
A: Yes, and their roles in the program must remain distinct.
Q: Was a subroutine worked out after computing machines had already existed for some time? ¶
Q: Are subroutines to implement mathematical functions? ¶
A: Yes, and in which the purpose of the subroutine is purely to compute one or more results whose values are entirely determined by the arguments passed to the subroutine.
Q: Is a subroutine its body? ¶
A: Yes, and which is the piece of program code that is executed when the subroutine is called or invoked.