A MIPS assembly language programmer must specify within each instruction which processor registers are going to be utilized. In the case of the MIPS architecture, all of the data manipulation instructions and the control instructions require their operands be in the register file. When developing code in a high-level language the use of descriptive variable names is extremely valuable for documentation purposes. Pseudocode facilitates collaboration in group projects. The original programmer usually is not the individual who will be making modifications or improvements to the code as the years pass. The use of high-level pseudocode is valuable during the initial development of a code module and will be especially helpful to the maintenance programmer. The logical structure of the code is more readily understood using a high-level notation. Anyone assigned the task of modifying the code will be extremely interested in the logical structure of the existing code. Pseudocode explains how the function is implemented. Upon return the pointer in (Mem$sp+4) will be pointing to the byte that follows the last hexadecimal digit in the string. A pointer to the string is passed to the function on the stack at Mem($sp+4). Scans a string of ASCII characters representing a hexadecimal number and returns the 32-bit binary equivalent value on the stack at Mem($sp+8). If the string does not correctly represent a decimal number error status value “1” is returned in register $v1 otherwise the status value returned is “0” for a valid decimal number.
Reads a string of decimal digits from the keyboard and returns the 32-bit binary equivalent in register $v0. The following are example functional descriptions for the classical I/O functions that are described in more detail later in this chapter:Ī 32-bit binary value is passed to the function in register $a0 and the hexadecimal equivalent is printed out right justified.Ī 32-bit binary value is passed to the function in register $a0 and the decimal equivalent is printed out right justified. The functional description must explain how arguments are passed to the function and how results are returned (if any). The functional description only describes what the function does, not how it is done. The main components of this documentation standard are:Ī functional description will provide the information anyone needs to know if they are searching for a function that would be useful is solving some larger programming assignment. The following pages provide a suggested minimal documentation standard. Every organization will have its own documentation standards. Good documentation will save programmers hours of time in analyzing how the existing code accomplishes its functionality, and will expedite the necessary modifications to the code. Often the programmer assigned the task of modifying a code module is not the same person who created the original version. Over time it is not unusual for the functional requirements of a code module to change which will require modifications be made to previously written code.
#HOW TO WRITE C CODE OF PALINDROME INTO MIPS ASSEMBY PROFESSIONAL#
Good documentation is valuable for student programmers as well as professional programmers. The importance of good program design and documentation can not be stressed too much.
0 kommentar(er)
