Differences

This shows you the differences between two versions of the page.

--- notes:data:fall2022:projects:sll3 [2022/10/09 05:05] – [BACKGROUND] abarbcal
+++ notes:data:fall2022:projects:sll3 [2022/10/19 21:42] (current) – [PROGRAM] dmuck
@@ Line 13: / Line 13: @@
 @date +'%Y%m%d%H%M%S' >> /var/public/$(SEMESTER)/$(DESIG)/$(PROJ)/.updates/.metrics/${USER}
 </cli>
+You might have to change the semester to fall2022 instead of having it check for the semester by checking the directory. You can delete what SEMESTER is set to and insert fall2022 instead.\\
+Note that if you are working on your pi there may be no semester file to begin with, so to create it simply use cd /usr/local/etc/ to go to the relevant location, use sudo su to gain root access, create a file named "semester", and insert "fall2022" into it. Then use can exit root with the "exit" command to decrease the likelihood of doing something you shouldn't.
 Then try building the project again.
@@ Line 28: / Line 33: @@
 =====SPECIFICATIONS=====
+Therefore, it is our task to modify our core node-list-processing functions to modify the qty value when necessary. When does the qty value change? When you add or remove nodes from the list!
+And to have a 'next' pointer ready to point to a linked list. For sll3, we will not focus much on 'next,' next will be part of sll4.
-What this all means
+Depending on how you coded your functions, these are functions you might be looking to modify:\\
-We have 5 modification tasks to do for full credit. These are:
   * mk(): Implement the new functionality of 'qty' and the next 'list'
-  * cp(): Make sure to copy the new properties of the struct 'list'
   * insert(): Add new functionality related to 'qty'
   * append(): Same as insert
   * obtain(): Opposite of insert() & append()
+  * cp(): Make sure to copy the new properties of the struct 'list'
+  * perhaps even clear().
+//Remember, these are list functions.//
 *Our task is to ask questions on Discord or in class and document our findings on this wiki page collaboratively, regarding the functionality of this project.
@@ Line 42: / Line 49: @@
 *For anybody interested in editing the wiki page, here is the dokuwiki user guide: https://www.dokuwiki.org/wiki:syntax#basic_text_formatting -Ash
 =====PROGRAM=====
-Inside list.h, the included header file given to you when you upgraded, and that you've had for the past few iterations of this project, was updated with additional variables. Two new variables were added to the list struct. Those are qty and next. Next is a pointer to the next list, we are now dealing with groups of linked lists. Qty contains the amount of nodes in the list. Other than that, nothing has changed inside the list.h file given to you. This project should take minimal time, don't be surprised if it seems too easy, that's why sll3 and sll4 are due both the week after break week. More detailed information about the types of qty and the next pointer are specified above in the specifications section.
+Inside list.h, the included header file given to you when you upgraded, and that you've had for the past few iterations of this project was updated with additional variables. Two new variables were added to the list struct.
+Those are qty and next.
+  * [next] is a pointer to the next list, we are now dealing with groups of linked lists. (myList -> next)
+  * [qty] contains the amount of nodes in the list. (myList -> qty)
+Other than that, nothing has changed inside the list.h file given to you. This project should take minimal time, don't be surprised if it seems too easy, that's why sll3 and sll4 are due both the week after break week. More detailed information about the types of qty and the next pointer are specified above in the specifications section.
+Remember- with the new quantity property, you only want to change it's value if you are adding/removing nodes to the list (Only in insert, append, and obtain). Also, be sure you check that you are not incrementing the quantity if inserting NULL to the list, or else your quantity will be incorrect (qty 1 number off on insert unit test). This should be checked for each function that inserts/removes nodes from the list.
 =====OUTPUT SPECIFICATIONS=====
 Nothing has changed in terms of output from your original five functions. Only add functionality of the new variables to the previously made functions.
 =====UNIT TESTS=====
-Unit Tests are again located inside bin/ after you compile. To compile, from the base sll3 directory, make clean(should be done every time but first time is not necessary) then make. Unit Tests will have more tests in each than previous, these tests are for your next and qty variables.
+Unit Tests are again located inside bin/ after you compile. To compile, from the base sll3 directory, make clean(should be done every time but first time is not necessary) then make.  An errors file will be created after running make, this may be helpful if things aren't compiling correctly. Unit Tests will have more tests in each than previous, these tests are for your next and qty variables.
+=====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 ./bin/unit-lobtain". Once in gdb the "run" command with start the program, and "break (line number)" will cause the program to stop at the specified line number. Once you have hit the breakpoint you can use "display (variable name)" to see the value of a variable at every step, "n" to step to the next line, and "continue" to continue running the program until the next breakpoint. Note that if you encounter a seg fault the program will tell the where the seg fault occurs, and you can use "run" again to restart the program.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools