Groupwork 3 Questions

Objectives

We would like to :

Address questions relating to groupwork 3.

Notes

Algorithm

    Initialize the calculator
    Open the file
    While there is data in the file
       read the command
       parse the command
       process the command

Questions:
1. When storing information on the calculator do we have a text file or just another file to keep that data when we close and reopen the calculator?
  - There is no reason to store information between sessions.
2. What does -Wpedantic do?
```
           Issue all the warnings demanded by strict ISO C and ISO C++;
           reject all programs that use forbidden extensions, and some
           other programs that do not follow ISO C and ISO C++.  For ISO
           C, follows the version of the ISO C standard specified by any

    From the g++ man page.
    
```
3. For Mayan how can we save the right positions for the values in mayan?
  - Divide the digit by 5, returning digit = a*5. Add a bars to the right of the number
  - Mod the digit by 5 returning digit % 5 = b. Add b dots to the left of the number
```
17 / 5 = 3   ||| 
17 % 5 = 2   ..
17 = ..||| 
```
4. How should error handling be implemented for invalid input formats within each number system?
5. What should the program do if a user tries to run an invalid command?
6. How can we check if the user input matches the correct format for its specified number system?
  - " You may assume that all commands are correct and in the correct format." from the assignment page.
7. Are there any specific limitations on the size of numbers within each number system?
  - They are given. All numbers will fit in an int.
8. How should negative numbers be represented and handled in each number system during calculations?
  - I would use signed integers.
9. How strictly should the output align? Should we use format specifiers, or should we manually add spaces?
  - It should match the specification.
10. When converting between number systems, what number system should the accumulator be in?
  - I would store all numbers as an int.
11. What is the most efficient way to convert between the different number systems, especially the more complex ones like Mayan and Modified Urnfield?
  - Convert all input to int.
  - Convert int to the desired output.
12. What data structures will be most suitable for storing and manipulating the accumulator and memory locations?
  - An array of ints for memory.
  - An int for the accumulator
  - A struct to group the two (or any other calculator data)
13. How can we make the code as adjustable as possible?
  - Many small functions.
14. How should we handle the positionless number system and its non-unique representations?
  - If the problem statement doesn't address this, you are free to do whatever you wish for output.
  - For input, you must handle any case.
15. In the case of input, if accumulator has a value, do we strictly overwrite that value? Are there any cases where we won't?
  - Yus, no.
16. Any advice on denoting given data types in memory? For example, I'm considering creating a struct DataTypeT to describe data in its decimal value and a string describing the data type
  - This is acceptable, but you really only need an int. After the data has been input, there is no further memory of the original base.
  -
17. I noticed in the provided computations.cmds file that there were lined using the ^ operand. Is it safe to presume that we are only computing the first number to the power of the second number and saving that to the accumulator? Are there any special instructions for this task?
  - Yes
18. Is it possible to receive more than one number in mathematical operations? Example: + 1:deci 1:deci 1:deci
  - No
19. What is the best way to store and organize the commands we read from the input file?
  - There is no need to store more than one command at a time.
20. Are there any special characters or rules we need to account for when parsing different base systems?
  - NO