Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » summer2015 » data » projects » dln0
haas:summer2015:data:projects:dln0

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
haas:summer2015:data:projects:dln0 [2015/06/21 14:08] – [In inc/list.h] wedgehaas:summer2015:data:projects:dln0 [2015/06/21 20:51] (current) – [node operation status codes] wedge
Line 84: Line 84:
 #define  DLN_ERROR           16   // 0x10, 0020, 00010000 #define  DLN_ERROR           16   // 0x10, 0020, 00010000
 #define  DLN_DEFAULT_FAIL    32   // 0x20, 0040, 00100000 #define  DLN_DEFAULT_FAIL    32   // 0x20, 0040, 00100000
-#define  DLN_RESERVED_CODE1  64   // 0x40, 0100, 01000000 +#define  DLN_INVALID         64   // 0x40, 0100, 01000000 
-#define  DLN_RESERVED_CODE2  128  // 0x80, 0200, 10000000+#define  DLN_RESERVED_CODE   128  // 0x80, 0200, 10000000
  
 // Function prototypes // Function prototypes
Line 94: Line 94:
 </code> </code>
  
-====list operation status codes==== +====node operation status codes==== 
-You'll notice the presence of a set of #define's in the list header file. These are intended to be used to report on various states of list status after performing various operations.+You'll notice the presence of a set of #define's in the data.h header file. These are intended to be used to report on various states of node status after performing various operations.
  
 They are not exclusive- in some cases, multiple states can be applied. The intent is that you will OR together all pertinent states and return that from the function. They are not exclusive- in some cases, multiple states can be applied. The intent is that you will OR together all pertinent states and return that from the function.
  
-  * **DLL_SUCCESS** - everything went according to plan, no errors encountered, average case +  * **DLN_SUCCESS** - everything went according to plan, no errors encountered, average case 
-  * **DLL_MALLOC_FAIL** - memory allocation failed (considered in error) +  * **DLN_MALLOC_FAIL** - memory allocation failed (considered in error) 
-  * **DLL_ALREADY_ALLOC** - memory has already been allocated (considered in error) +  * **DLN_ALREADY_ALLOC** - memory has already been allocated (considered in error) 
-  * **DLL_NULL** - result is NULL (probably in error) +  * **DLN_NULL** - result is NULL (probably in error) 
-  * **DLL_EMPTY** - result is an empty list (may or may not be in error) +  * **DLN_DEFAULT_FAIL** - default state of unimplemented functions (default error) 
-  * **DLL_DEFAULT_FAIL** - default state of unimplemented functions (default error) +  * **DLN_ERROR** - some error occurred 
-  * **DLL_FAIL** - some error occurred+  * **DLN_INVALID** - invalid use (NULL pointer) 
 +  * **DLN_RESERVED_CODE** - reserved for future use (not used at present time)
  
-For example, in the case of "DLL_MALLOC_FAIL", there are actually a total of three states raised: +For example, in the case of "DLN_MALLOC_FAIL", there are actually a total of three states raised: 
-  * DLL_FAIL (a problem has occurred) +  * DLN_ERROR (a problem has occurred) 
-  * DLL_MALLOC_FAIL (a problem has occurred when using malloc()) +  * DLN_MALLOC_FAIL (a problem has occurred when using malloc()) 
-  * DLL_NULL (no memory allocated, so list cannot be anything but NULL)+  * DLN_NULL (no memory allocated, so node cannot be anything but NULL)
  
 ALL THREE states must be returned from the function in question should such an occurrence take place. ALL THREE states must be returned from the function in question should such an occurrence take place.
 +
 +You'll notice these #defines map to numeric values, and particular ones at that. This is to our supreme advantage: if you understand how numbers work, you should have an easy time of working with these status codes.
 ====node library==== ====node library====
 In **src/node/**, you will find skeletons of what was previously there, ready for you to re-implement. In **src/node/**, you will find skeletons of what was previously there, ready for you to re-implement.
Line 132: Line 135:
 =    Verifying Doubly-Linked Node Functionality    = =    Verifying Doubly-Linked Node Functionality    =
 ==================================================== ====================================================
-  [mknode] Total:   5, Matches:   5, Mismatches:   0 + [mknode] Total:  12, Matches:  12, Mismatches:   0 
-  [cpnode] Total:   6, Matches:   6, Mismatches:   0 + [cpnode] Total:  15, Matches:  15, Mismatches:   0 
-  [rmnode] Total:   2, Matches:   2, Mismatches:   0+ [rmnode] Total:   4, Matches:   4, Mismatches:   0
 ==================================================== ====================================================
- [RESULTS] Total:  13, Matches:  13, Mismatches:   0+[RESULTS] Total:  31, Matches:  31, Mismatches:   0
 ==================================================== ====================================================
 lab46:~/src/data/dln0$  lab46:~/src/data/dln0$ 
haas/summer2015/data/projects/dln0.1434895732.txt.gz · Last modified: 2015/06/21 14:08 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