Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » fall2014 » data » projects » sll1
haas:fall2014:data:projects:sll1

Differences

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

Link to this comparison view

Next revision		Previous revision
haas:fall2014:data:projects:sll1 [2014/10/05 13:05] – created wedgehaas:fall2014:data:projects:sll1 [2014/10/16 20:21] (current) – [Errata] wedge
Line 11: Line 11:
 This section will document any updates applied to the project since original release: This section will document any updates applied to the project since original release:
  
-  * __revision #__: <description> (DATESTRING)+  * __revision 1__: I discovered a typo in the unit tests for swapnode and rmlist, the for loop iterators were going the wrong way. FIXED. (20141016)
  
 =====Objective===== =====Objective=====
Line 32: Line 32:
 </code> </code>
  
-As a suggestion, I'd recommend implementing them in the order listed above, starting with **obtain()**. By doing this, the functionality will be available to use in your implementation of the other functions.+As a suggestion, I'd recommend implementing them in the order listed above, starting with **searchlist()** and then **obtain()**. By doing this, you get to review a bit from the previous weeks (**searchlist()**) and then continue with base functionality (**obtain()**), which will help you in your implementation of the other functions.
  
 An important perspective to keep when implementing these list functions is to be mindful of what functionality can be a unit of something else. Do not reinvent the wheel- utilize functions you've written- it will shorten your code, and reduce the chance of error. Plus, that IS the intent.. to have each function be specific and focused on its particular task; to do one thing, and do that one thing extremely well. We can then use them as base units to build more sophisticated functionality. An important perspective to keep when implementing these list functions is to be mindful of what functionality can be a unit of something else. Do not reinvent the wheel- utilize functions you've written- it will shorten your code, and reduce the chance of error. Plus, that IS the intent.. to have each function be specific and focused on its particular task; to do one thing, and do that one thing extremely well. We can then use them as base units to build more sophisticated functionality.
Line 39: Line 39:
  
 ====list library==== ====list library====
-In **src/list/**, you will find 6 new C files:+In **src/list/**, you will find 4 new C files:
  
   * **obtain.c**   - which will house the list obtain function (to disconnect nodes from a list)   * **obtain.c**   - which will house the list obtain function (to disconnect nodes from a list)
haas/fall2014/data/projects/sll1.1412514353.txt.gz · Last modified: 2014/10/05 13:05 by wedge

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki