notes:data:fall2022:projects:dls0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| notes:data:fall2022:projects:dls0 [2022/11/07 15:19] – [BACKGROUND] mfee1 | notes:data:fall2022:projects:dls0 [2022/11/11 01:30] (current) – [SPECIFICATIONS] zswartwo | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| - | =====SPECIFICATIONS===== | + | cd=====SPECIFICATIONS===== |
| The top of the stack follows the list in reverse order. The top of the stack will be equal to the last node of the list. | The top of the stack follows the list in reverse order. The top of the stack will be equal to the last node of the list. | ||
| + | |||
| + | myStack -> top = myList -> last | ||
| + | |||
| There will be approximately 7 functions, will have to confirm that once you upgrade. | There will be approximately 7 functions, will have to confirm that once you upgrade. | ||
| These new functions go as follows: | These new functions go as follows: | ||
| Line 20: | Line 23: | ||
| Do your best to not reinvent the wheel. This project contains a lot of work with node's and list's and thoughtful use of previously made functions relating to those data structures will lead to cleaner code. This is also a time to test your previously made functions in an actual use environment, | Do your best to not reinvent the wheel. This project contains a lot of work with node's and list's and thoughtful use of previously made functions relating to those data structures will lead to cleaner code. This is also a time to test your previously made functions in an actual use environment, | ||
| + | |||
| + | ===Applying List functions in stack functions=== | ||
| + | Below are pairings of stack functions on the left, and list functions that could be very useful in accomplishing these stack functions on the right. \\ | ||
| + | mk.c -> mklist \\ | ||
| + | push.c -> append \\ | ||
| + | pop.c -> obtain \\ | ||
| + | cpstack.c -> mkstack, cplist \\ | ||
| + | peek.c -> cpnode \\ | ||
| + | rmstack.c -> rmlist \\ | ||
| + | |||
| + | |||
| + | ====USE YOUR LIST FUNCTIONS TO HANDLE NODES WITHIN THE STACKS==== | ||
| **KEY NOTE:** Remember that the dereferenced version of the double pointers inside other functions you use should be NULL. Most of the functions previously made should have had an error if the dereferenced list/node was not NULL. | **KEY NOTE:** Remember that the dereferenced version of the double pointers inside other functions you use should be NULL. Most of the functions previously made should have had an error if the dereferenced list/node was not NULL. | ||
| Line 27: | Line 42: | ||
| *For anybody interested in editing the wiki page, here is the dokuwiki user guide: https:// | *For anybody interested in editing the wiki page, here is the dokuwiki user guide: https:// | ||
| =====PROGRAM===== | =====PROGRAM===== | ||
| - | Inside the stack are 3 different objects, a node, a list, and the size of the stack. The node is the top of the stack, and follows the last node of the list. For the purpose of your push and pop functions, new nodes from push should go to the end of the list, and that should be the new top. For pop, it should take off the end of the list, and reassign the new top, which is the last node in the list. | + | Inside the stack are 3 different objects, a node, a list, and the size of the stack. The node is the top of the stack, and follows the last node of the list. For the purpose of your push and pop functions, new nodes from push should go to the end of the list, and that should be the new top. For pop, it should take off the end of the list, and reassign the new top, which is the last node in the list. Also, you can make use of the make command -make use-test-reference. This uses a working implementation of object files from the previous dllX projects, and can very much help you if your previous projects did not pass all unit tests. |
| =====OUTPUT SPECIFICATIONS===== | =====OUTPUT SPECIFICATIONS===== | ||
| No output should be visible outside of testing purposes inside unit tests. Functions will modify the corresponding list/ | No output should be visible outside of testing purposes inside unit tests. Functions will modify the corresponding list/ | ||
| =====UNIT TESTS===== | =====UNIT TESTS===== | ||
notes/data/fall2022/projects/dls0.1667834371.txt.gz · Last modified: 2022/11/07 15:19 by mfee1
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
