Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » fall2022 » data » projects » ael0
haas:fall2022:data:projects:ael0

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:fall2022:data:projects:ael0 [2022/08/18 14:20] – [Background] wedgehaas:fall2022:data:projects:ael0 [2022/08/18 15:02] (current) – [Submit Tool Usage] wedge
Line 87: Line 87:
 ====menu==== ====menu====
  
-  * Presents the user with a menu (reference sample output below for menu +  * Presents the user with a menu (reference sample output below for menu specifications), having the listed features.
-    specifications), having the listed features.+
     * use numbers for input (don't get fancy)     * use numbers for input (don't get fancy)
-    * use numbers  for the functionalities given (it will  make it easier +    * use numbers  for the functionalities given (it will  make it easier for me to evaluate) 
-      for me to evaluate) +    * accept menu and general program input from STDIN (value followed by ENTER). 
-    * accept menu and general program input from STDIN (value followed by +      * fscanf() would  be an excellent function  to familiarize yourself with.
-      ENTER). +
-      * fscanf() would  be an excellent function  to familiarize yourself +
-        with.+
  
 <cli> <cli>
Line 116: Line 112:
   * build list   * build list
  
-    * prompt the  user to enter number after number,  appending it to the +    * prompt the  user to enter number after number,  appending it to the list, until the user terminates the action by entering a -1. Prompt will display to STDERR.
-      list, until the user terminates the action by entering a -1. Prompt +
-      will display to STDERR.+
     * We will check for a -1 in the array to signify the end of our  list     * We will check for a -1 in the array to signify the end of our  list
-    * if  you're  crafty  about it,  this  doesn't have  to  be a  unique +    * if  you're  crafty  about it,  this  doesn't have  to  be a  unique function, but a loop (even from  the menu code) calling an existing function.
-      function, but a loop (even from  the menu code) calling an existing +
-      function.+
  
 <cli> <cli>
Line 139: Line 131:
  
   * display list forward   * display list forward
-    * From  the first (zero-th) element  of the array clear  through (and +    * From  the first (zero-th) element  of the array clear  through (and including) to the element containing the -1,
-      including) to the element containing the -1,+
     * display the contained numbers, along with their array index.     * display the contained numbers, along with their array index.
-    * as   output  is  a  core necessity  of  displaying,  your  function +    * as   output  is  a  core necessity  of  displaying,  your  function displaying the list can and should perform output. 
-      displaying the list can and should perform output. +    * I  want you to  have some sort  of **display()** function;  you can have a separate one  for  displaying  forward (**displayf()**)  and backward (**displayb()**), or one combining both functionalities. I leave that up to you.
-    * I  want you to  have some sort  of **display()** function;  you can +
-      have a separate one  for  displaying  forward (**displayf()**)  and +
-      backward (**displayb()**), or one combining both functionalities. I +
-      leave that up to you.+
  
 <cli> <cli>
Line 164: Line 151:
  
   * display list backward   * display list backward
-    * From the list termination value (the -1 following the last element) +    * From the list termination value (the -1 following the last element) to the beginning.
-      to the beginning.+
     * display the contained numbers, along with their array index.     * display the contained numbers, along with their array index.
-    * as   output  is  a  core necessity  of  displaying,  your  function +    * as   output  is  a  core necessity  of  displaying,  your  function displaying the list is where the list display output takes place.
-      displaying the list is where the list display output takes place.+
  
 <cli> <cli>
Line 191: Line 176:
     * prompt for array index (prompt will display to STDERR)     * prompt for array index (prompt will display to STDERR)
     * accept new value from the user     * accept new value from the user
-    * without  destroying  any  array contents,  place  new value  BEFORE +    * without  destroying  any  array contents,  place  new value  BEFORE specified array index
-      specified array index+
       * this will likely involve shifting some data       * this will likely involve shifting some data
-    * this    functionality   should  be   encapsulated  in   a  discrete +    * this    functionality   should  be   encapsulated  in   a  discrete **insert()** function
-      **insert()** function+
       * do NOT use global variables; pass and return necessary data       * do NOT use global variables; pass and return necessary data
-    * no output of any kind should take place in **insert()**, merely the +    * no output of any kind should take place in **insert()**, merely the specified list processing.
-      specified list processing.+
  
 <cli> <cli>
Line 226: Line 208:
     * prompt for array index (prompt will display to STDERR)     * prompt for array index (prompt will display to STDERR)
     * accept new value from the user     * accept new value from the user
-    * without  destroying  any  array  contents,  place new  value  AFTER +    * without  destroying  any  array  contents,  place new  value  AFTER specified array index
-      specified array index+
       * this will likely involve shifting some data       * this will likely involve shifting some data
-    * this  functionality   should  be   encapsulated  in   a    discrete +    * this  functionality   should  be   encapsulated  in   a    discrete **append()** function
-      **append()** function+
       * do  NOT  use any global variables; pass and return necessary data       * do  NOT  use any global variables; pass and return necessary data
-    * no output of any kind should take place in **append()**, merely the +    * no output of any kind should take place in **append()**, merely the specified list processing.
-      specified list processing.+
  
 <cli> <cli>
Line 268: Line 247:
   * obtain from list   * obtain from list
     * prompt for array index (prompt will display to STDERR)     * prompt for array index (prompt will display to STDERR)
-    * obtain value  at array index and place it  in a standalone variable +    * obtain value  at array index and place it  in a standalone variable (to be displayed to STDOUT) 
-      (to be displayed to STDOUT) +    * adjust  array  contents to  no longer  include this  obtained value (we've removed it from the list) 
-    * adjust  array  contents to  no longer  include this  obtained value +    * this  functionality   should  be   encapsulated   in    a  discrete **obtain()** function
-      (we've removed it from the list) +
-    * this  functionality   should  be   encapsulated   in    a  discrete +
-      **obtain()** function+
       * do NOT use global variables; pass and return necessary data       * do NOT use global variables; pass and return necessary data
-    * The "The value you obtained:"  message should NOT take place within +    * The "The value you obtained:"  message should NOT take place within your **obtain()** function; no output of any kind should take place in **obtain()**, merely the specified list processing.
-      your **obtain()** function; no output of any kind should take place +
-      in **obtain()**, merely the specified list processing.+
  
 <cli> <cli>
Line 309: Line 283:
  
   * clear list   * clear list
-    * empty the array, leaving it in an initial state (-1 at the 0 index, +    * empty the array, leaving it in an initial state (-1 at the 0 index, more places if it messes up your reverse list display) 
-      more places if it messes up your reverse list display) +    * if  you're  crafty  about it,  this  doesn't have  to  be a  unique function, but a loop (even from the menu code) calling  an existing function.
-    * if  you're  crafty  about it,  this  doesn't have  to  be a  unique +
-      function, but a loop (even from the menu code) calling  an existing +
-      function.+
  
 ===quit=== ===quit===
  
   * quit   * quit
-    * Each menu item  should correspond to a discrete  activity you'll be +    * Each menu item  should correspond to a discrete  activity you'll be performing on the list or program, and each item is implemented out in separate functions  (with the exception of the  quit option, and possibly the "build"  and "clear" options, although  you can deploy functions for those too, if you really want). 
-      performing on the list or program, and each item is implemented out +  * Additionally, with the  exception of displaying the  list, you should perform no I/O within any of these functions (do it all in main(), or where-ever your core menu logic is located). 
-      in separate functions  (with the exception of the  quit option, and +    * basically, when appending, have a  function that handles the actual append operation, but  do the input and output  in/around your menu code  (so your  append()  function basically  just manipulates  the list). 
-      possibly the "build"  and "clear" options, although  you can deploy +  * This  list, for  now, will  be  housed within  a statically  declared integer  array  (of  20  elements).   You  are  to  perform  whatever manipulations are needed on that array. 
-      functions for those too, if you really want). +    * What if  you exceed  the array?  You exceed  it... the  program may crash and  or infinitely loop  or otherwise be  unpredictable. This program is  really just  to start you  practicing on  the important operations of  inserting, appending,  and obtaining. For  now, just assume the user will always do the right thing and never completely fill up the list. 
-  * Additionally, with the  exception of displaying the  list, you should +  * A  "list" is,  for all  intents and  purposes, a  sequence of  values located  together. In  this  case, they  do not  have  to be  sorted, merely considered  part of  a group  or category.  Here, we  will use the  containing  features of  the  array  to accomplish  that  (while simultaneously reviewing C!)
-    perform no I/O within any of these functions (do it all in main(), or +
-    where-ever your core menu logic is located). +
-    * basically, when appending, have a  function that handles the actual +
-      append operation, but  do the input and output  in/around your menu +
-      code  (so your  append()  function basically  just manipulates  the +
-      list). +
-  * This  list, for  now, will  be  housed within  a statically  declared +
-    integer  array  (of  20  elements).   You  are  to  perform  whatever +
-    manipulations are needed on that array. +
-    * What if  you exceed  the array?  You exceed  it... the  program may +
-      crash and  or infinitely loop  or otherwise be  unpredictable. This +
-      program is  really just  to start you  practicing on  the important +
-      operations of  inserting, appending,  and obtaining. For  now, just +
-      assume the user will always do the right thing and never completely +
-      fill up the list. +
-  * A  "list" is,  for all  intents and  purposes, a  sequence of  values +
-    located  together. In  this  case, they  do not  have  to be  sorted, +
-    merely considered  part of  a group  or category.  Here, we  will use +
-    the  containing  features of  the  array  to accomplish  that  (while +
-    simultaneously reviewing C!)+
  
 =====Further output requirements===== =====Further output requirements=====
Line 493: Line 444:
  
   * Project must be submit on time, by the posted deadline.   * Project must be submit on time, by the posted deadline.
-    * Late submissions will lose 33%  credit per day, with the submission +    * Late submissions will lose 33%  credit per day, with the submission window closing on the 3rd day following the deadline.
-      window closing on the 3rd day following the deadline.+
   * All code must compile cleanly (no warnings or errors)   * All code must compile cleanly (no warnings or errors)
-    * Compile with the **-Wall** and **--std=gnu99** compiler flags +    * Compile with the **-Wall** and **--std=gnu18** compiler flags 
-    * all requested functions must  be implemented in the related library +    * all requested functions must  be implemented in the related library or program 
-      or program +    * all  requested functionality  must conform  to stated  requirements (either on  this project page or  in comment banner in  source code files themselves).
-    * all  requested functionality  must conform  to stated  requirements +
-      (either on  this project page or  in comment banner in  source code +
-      files themselves).+
   * Executed programs must display in a manner similar to provided output   * Executed programs must display in a manner similar to provided output
-    * output  formatted,  where applicable,  must match  that of  project +    * output  formatted,  where applicable,  must match  that of  project requirements
-      requirements+
   * Processing must be correct based on input given and output requested   * Processing must be correct based on input given and output requested
   * Output, if applicable, must be correct based on values input   * Output, if applicable, must be correct based on values input
Line 510: Line 456:
   * Code must be commented   * Code must be commented
     * Any "to be implemented" comments **MUST** be removed     * Any "to be implemented" comments **MUST** be removed
-      * these   "to  be  implemented"   comments,  if  still  present  at +      * these   "to  be  implemented"   comments,  if  still  present  at evaluation time, will result in points being deducted. 
-        evaluation time, will result in points being deducted. +      * Sufficient  comments  explaining  the point  of  provided   logic **MUST** be present
-      * Sufficient  comments  explaining  the point  of  provided   logic +
-        **MUST** be present+
   * No global variables, no goto statements, no manual calling of main()!   * No global variables, no goto statements, no manual calling of main()!
-  * at minimum, a  discrete **append()**, **insert()**, **obtain()**, and +  * at minimum, a  discrete **append()**, **insert()**, **obtain()**, and some form of list display functions. 
-    some form of list display functions. +    * with  the exception of  your display function(s),  no I/O is  to be performed in any of your functions.
-    * with  the exception of  your display function(s),  no I/O is  to be +
-      performed in any of your functions.+
   * Track/version the source code in your lab46 repository   * Track/version the source code in your lab46 repository
   * Do NOT use any **goto** statements.   * Do NOT use any **goto** statements.
-  * Submit  a copy of  your source code to  me using the  **submit** tool +  * Submit  a copy of  your source code to  me using the  **submit** tool (**make submit** will do this) by the deadline.
-    (**make submit** will do this) by the deadline.+
  
 ====Submit Tool Usage==== ====Submit Tool Usage====
Line 530: Line 471:
  
 <cli> <cli>
-lab46:~/src/data/ael0$ submit data ael0 ael0.c+lab46:~/src/SEMESTER/data/ael0$ submit data ael0 ael0.c
 Submitting data project "ael0": Submitting data project "ael0":
     -> ael0.c(OK)      -> ael0.c(OK) 
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
-lab46:~/src/data/ael0$ +lab46:~/src/SEMESTER/data/ael0$ 
 </cli> </cli>
  
Line 555: Line 496:
 Additionally: Additionally:
  
-  * Solutions not abiding  by spirit of project will be  subject to a 25% +  * Solutions not abiding  by spirit of project will be  subject to a 50% overall deduction 
-    overall deduction +  * Solutions  not  utilizing descriptive  why and  how comments  will be subject to a 25% overall deduction 
-  * Solutions  not  utilizing descriptive  why and  how comments  will be +  * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction 
-    subject to a 25% overall deduction +  * Solutions not organized and easy to  read (assume a terminal at least 90 characters wide, 40 characters tall)  are subject to a 25% overall deduction
-  * Solutions not utilizing indentation to promote scope and clarity will +
-    be subject to a 25% overall deduction +
-  * Solutions not organized and easy to  read (assume a terminal at least +
-    90 characters wide, 40 characters tall)  are subject to a 25% overall +
-    deduction+
  
haas/fall2022/data/projects/ael0.1660832448.txt.gz · Last modified: 2022/08/18 14:20 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