
the dev guide suggests that handling cs/cu is under proposed, which I assume is meant for future iteration. However, the program does attempt to handle CS/CU in the current iteration--thought not accurately. Furthermore, this happens when user attempts to enter S or U not cs/cu as mentioned.
the dev guide suggests that handling cs/cu is under proposed, which I assume is meant for future iteration. However, the program does attempt to handle CS/CU in the current iteration--thought not accurately. Furthermore, this happens when user attempts to enter S or U not cs/cu as mentioned.