notes:data:fall2022:projects:dln0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| notes:data:fall2022:projects:dln0 [2022/10/27 14:07] – [PROGRAM] zswartwo | notes:data:fall2022:projects:dln0 [2022/10/27 15:16] (current) – bolsen1 | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| If you recall from the sll project, info is the contents of the node. Info now has the potential to hold different types of data, not just an unsigned char, BUT it still only holds one at a time. | If you recall from the sll project, info is the contents of the node. Info now has the potential to hold different types of data, not just an unsigned char, BUT it still only holds one at a time. | ||
| The type of data it could hold is an unsigned char value, point to another Node anywhere else (could be in another group, on another list, so on), and a pointer that could point to any other type of pointer (only pointers though). In this project, we only need to worry about the node's left and right, and payload. | The type of data it could hold is an unsigned char value, point to another Node anywhere else (could be in another group, on another list, so on), and a pointer that could point to any other type of pointer (only pointers though). In this project, we only need to worry about the node's left and right, and payload. | ||
| + | |||
| + | Remember that there can only be one return statement per function, I suggest having a variable that contains the exit code and change that along with the flow of the program in case of errors. | ||
| =====SPECIFICATIONS===== | =====SPECIFICATIONS===== | ||
| Line 39: | Line 41: | ||
| Some general advice for each function:\\ | Some general advice for each function:\\ | ||
| mknode() - don't forget about the left and right pointers, explore into /inc/ to see what each node contains\\ | mknode() - don't forget about the left and right pointers, explore into /inc/ to see what each node contains\\ | ||
| - | cpnode() - make sure to copy the entire payload, union has different types of different sizes so don't just copy the smallest one\\ | + | cpnode() - make sure to copy the entire payload, union has different types of different sizes so don't just copy the smallest one. It may be a good idea to use your previously created mk function. Remember, do not reinvent the wheel\\ |
| rmnode() - not too much needed for this one, make sure you have the sufficient error checks, set to NULL after deallocation\\ | rmnode() - not too much needed for this one, make sure you have the sufficient error checks, set to NULL after deallocation\\ | ||
| + | ===Recommended order of creation=== | ||
| + | 1.Mknode\\ | ||
| + | 2.Rmnode\\ | ||
| + | 3.Cpnode\\ | ||
| =====DEBUGGING===== | =====DEBUGGING===== | ||
| Useful tools for debugging issues are gdb and examining the test files themselves. to utilize gdb, run the test program with the gdb command (not make check), with a command that might look like "gdb ./ | Useful tools for debugging issues are gdb and examining the test files themselves. to utilize gdb, run the test program with the gdb command (not make check), with a command that might look like "gdb ./ | ||
notes/data/fall2022/projects/dln0.1666879650.txt.gz · Last modified: 2022/10/27 14:07 by zswartwo
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
