Differences

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

--- notes:data:fall2022:projects:dll1 [2022/10/29 23:39] – [SPECIFICATIONS] hcordell
+++ notes:data:fall2022:projects:dll1 [2022/11/03 16:10] (current) – [UNIT TESTS] zswartwo
@@ Line 4: / Line 4: @@
 This week we are working on the following functions:
-  * Obtain
+  * obtain
-  * Empty
+  * empty
   * rmlist
   * compare
@@ Line 19: / Line 19: @@
 *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=====
+It should be noted that the new compare is quite similar to the sllx version, therefore drawing inspiration from the code one wrote previously may be of assistance.
+For the new //rmlist// function, like the one in the previous sllx projects, it would be wise to work on the //empty// function first (similar to that of the //clear// function in the sllx projects). That way when you want to deallocate a list, you can call the //empty// function to clear up the nodes within the list to ensure there is no memory leak.
+**NOTE** If you are trying to work on this project without a fully functional dll0 library, you are still able to complete this project, and get full credit (if new implementations pass all the test cases). To do this, in your root folder of dll1 type: **make use-test-reference**. Rather than using your implementations of previous functions, your make will now use working implementations ONLY of functions from previous dllX's.
 =====OUTPUT SPECIFICATIONS=====
 No output to stdout for any of these functions, all functions should modify the list in some way, shape, or form.
 =====UNIT TESTS=====
-Total of 162 tests. Unit tests are called with make check, similar to every other week. Safe practice to **make clean** before every **make** to ensure old results are cleaned up. Tests are split amongst all the functions, with 7 going to empty and rmlist. Compare, Swap, Sort, and Obtain have 12, 31, 48, and 57 tests respectively. While unit tests do a good job of ensuring basic functionality, ensure that your functions can work with any provided input. To be specific, if you're going to use swap inside sort(a good idea), make sure your swap can handle functions side by side anywhere in the list. The unit test for swap does not check for this.
+Total of 162 tests. Unit tests are called with make check, similar to every other week. Safe practice to **make clean** before every **make** to ensure old results are cleaned up.  There will be an errors file created after running make, it’s a good idea to check this as well.  Tests are split amongst all the functions, with 7 going to empty and rmlist. Compare, Swap, Sort, and Obtain have 12, 31, 48, and 57 tests respectively. While unit tests do a good job of ensuring basic functionality, ensure that your functions can work with any provided input. To be specific, if you're going to use swap inside sort(a good idea), make sure your swap can handle functions side by side anywhere in the list. The unit test for swap does not check for this.
+Additionally, if one wishes to be shown any compiling errors/warnings immediately, one could use "make debug" to do so, as this will reroute the contents of the make to stdout instead of the errors file.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools