mrsarno / pycalculate Goto Github PK

PyCalculate currently operates on the 'everything is fine' assumption.

It needs to analyse user input, and throw error messages & re-request information when bad info is provided by the user.

Where the program prompts the user for input, it shouldn't rely on the user specifically providing e.g. lower-case input.

An example of where the program does this;

while more_calc_input != "y" and more_calc_input != "n":

The initial version of the program only allows a user to perform a single calculation each time the program is run.

It should offer the choice of either performing an additional calculation or closing it.

In some cases string concatenation (thing + stuff) is used, and in other cases it isn't (thing, stuff).

The status quo is functional, but in the interests of clean, quality code it should probably be standardised.

PyCalculate currently requests that the user provide +, -, x, or / as an operator.

While those are the only ones it will ever encourage, it should also accept other common examples, such as;

• * (multiply)
• ÷ (divide)
• X (multiply)
• etc.

The plan is to silently accept those, but encourage the four I judge to be the most common. While programmers might favour the asterisk I think the average user favours the letter x, and the division sign is fancy but comparatively difficult to enter using a keyboard.

A very permissive one (Unlicense?)

Currently, the program asks the user for their name and then... never brings it up again.

The loop (see #3) should begin by greeting the user by their name & then request numbers & the operator.

If it feels creepy or forced, it can be removed without worry.

Do after #11.

It's possible that interviewers (in a hurry) will be interested in checking it out.