Lab46 Wiki

User Tools

Site Tools

You are here: start » notes » data » fall2022 » projects » sln1
notes:data:fall2022:projects:sln1

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
notes:data:fall2022:projects:sln1 [2022/09/15 00:01] – [UNIT TESTS] rcorcor1notes:data:fall2022:projects:sln1 [2022/09/15 02:22] (current) – [Useful commands] bbarrow1
Line 5: Line 5:
 =====SPECIFICATIONS===== =====SPECIFICATIONS=====
  
-In simple words, after you've grabbed the project files, it is our task to edit the cp.c mk.c, and rm.c files inside the '//sln1/src/node/ //' directory and make them work.+In simple words, after you've grabbed the project files, it is our task to edit the cp.c mk.c, and rm.c files inside the '//sln1/src/node/ //' directory and make them work. cp.c standing for copy, mk.c is our program that creates node, and rm.c is our program to remove nodes.
  
 We have many files for reference at our disposal. The most important files to execute, read, and analyze are contained within the '//sln1/unit/node/ //' directory. These source code files will be your guides, to get your files to work. We have many files for reference at our disposal. The most important files to execute, read, and analyze are contained within the '//sln1/unit/node/ //' directory. These source code files will be your guides, to get your files to work.
Line 11: Line 11:
 As explained down below in the Unit Test section, another set of important files is contained within the '//sln1/bin/ //' directory. Run these files for testing. As explained down below in the Unit Test section, another set of important files is contained within the '//sln1/bin/ //' directory. Run these files for testing.
  
-//You will find a "node.h" file in the provided include directory (sln1/inc/node.h) which provides a **struct node** that will serve as the structure of the Node that you will be manipulating //+//You will find a "node.h" file in the provided include directory (sln1/inc/node.h) which provides a **struct node** that will serve as the structure of the Node that you will be manipulating // (may find information pertaining to the various node options)
  
 The mknode() program should allocate memory for a new node, verify that the allocation was successful, and then populate and return the address to the new node. The rmnode() program should only de-allocate the node passed into the program.  The mknode() program should allocate memory for a new node, verify that the allocation was successful, and then populate and return the address to the new node. The rmnode() program should only de-allocate the node passed into the program. 
Line 28: Line 28:
 </blockquote> </blockquote>
 =====PROGRAM===== =====PROGRAM=====
-Program should be able to perform specifications displayed inside the files. For example, inside src/node/mk.c, rm.c, and cp.c should be able to make nodes, remove nodes, and copy nodes, respectively. Some files inside app/node/ have little to no needed code and only test your src/node/ files. If your files are made correctly and to project specifications it should work well and similar to some of your sln0 pseudocode. Most, if not all, of the specifications will be commented inside the files with what you need to do. +Program should be able to perform specifications displayed inside the files. For example, inside src/node/mk.c, rm.c, and cp.c should be able to make nodes, remove nodes, and copy nodes, respectively. Some files inside app/node/ have little to no needed code and only test your src/node/ files. If your files are made correctly and to project specifications it should work well and similar to some of your sln0 pseudocode. Most, if not all, of the specifications will be commented inside the files with what you need to do.\\  
 +When making the three programs, first look at "node.h" as it will tell you how to go about programing them, for example when making a node you know that the node will have a node->right and a node->info. 
 +When copying the node you do not need to allocate space, rather use an existing function. 
 +When removing you should think about how malloc works and what the node would become. 
 +In each of these codes think about what it is you want to be returned.\\ 
 **Directories containing vital project information:** **Directories containing vital project information:**
-  * ''/inc/'' contains your header files used in most programs+  * ''/inc/'' contains your header files used in most programs(contains options used such as "right" and "info")
   * ''/unit/node/'' contains your unit tests for mk.c, rm.c, and cp.c   * ''/unit/node/'' contains your unit tests for mk.c, rm.c, and cp.c
   * ''/src/node/'' contains the mk.c, rm.c, and cp.c files   * ''/src/node/'' contains the mk.c, rm.c, and cp.c files
Line 78: Line 81:
 </cli> </cli>
  
-If you run into any issues (perhaps from running make **not** in the base directory), try **make clean && make** to rebuild your project.  Typing **cat errors** at the prompt, may also be helpful in figuring out what’s going wrong. +If you run into any issues (perhaps from running make **not** in the base directory), try **make clean && make** to rebuild your project.  Typing **cat errors** at the prompt, may quite beneficial in figuring out what exactly is making your unit tests come back as mismatches. You can also run **make debug** instead of **make**, to get the errors immediately. 
-Cat errors can be quite beneficial in figuring out what exactly is making your unit tests come back as mismatches. + 
 +You can run single unit tests via **bin/<unit test name>**.
 =====Useful commands===== =====Useful commands=====
 Get a full list of options: Get a full list of options:
Line 94: Line 98:
 <cli> <cli>
 USERNAME@lab46:~/src/fall2022/sln1$ make clean USERNAME@lab46:~/src/fall2022/sln1$ make clean
 +</cli>
 +
 +Make and print errors immediately:
 +<cli>
 +USERNAME@lab46:~/src/fall2022/sln1$ make debug
 </cli> </cli>
  
Line 106: Line 115:
 </cli> </cli>
  
-Upgrade to the next project (sll0)+Upgrade to the next project (sll0)\\  
 +**Note this takes current sln1 directory and copies your codes into sll0, use only when done.**
 <cli> <cli>
 USERNAME@lab46:~/src/fall2022/sln1$ make upgrade-sll0 USERNAME@lab46:~/src/fall2022/sln1$ make upgrade-sll0
Line 122: Line 132:
 Before running the 'make' command, remove the "errors" file because running make appends new errors onto the end of the errors file. This means that when you read the errors file you will be reading old errors that may or may not exist since 'make' does not delete the old errors file in this project. Before running the 'make' command, remove the "errors" file because running make appends new errors onto the end of the errors file. This means that when you read the errors file you will be reading old errors that may or may not exist since 'make' does not delete the old errors file in this project.
  
-Also, use the 'make clean' command before running 'make' after adjusting your code, I found that I was rerunning old executables with non-functional code even after I made changes to it until I ran 'make clean'.+Also, use the 'make clean' command before running 'make' after adjusting your code, I found that I was rerunning old executables with non-functional code even after I made changes to it until I ran 'make clean'. If your code is failing to compile or if it is mismatched, try a make clean as well.
notes/data/fall2022/projects/sln1.1663200067.txt.gz · Last modified: 2022/09/15 00:01 by rcorcor1

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