Quadratic formula on calculator program

There are two imaginary solutions. Step 1: Calculate the delta The resolution of a quadratic equation necessarily passes by the calculation of the discriminant also called delta.

Thus, you will find 4 steps after entering the data in fields a, b and c: Equation: Resumes the total formatting of your second degree equation. The Discriminant delta : That will let you know the number of solutions. Resolution: For all calculation steps. Solution s : Achieving the long-awaited result. Related Tools. Both will result in the same final result, it is up to you which you would like to use. Grab your calculator charging cable, plug your calculator into your computer, and open TI Connect CE.

Make sure your calculator is turned on! And there you have it! A Quadratic Equation solver! Its great for checking work on problems! Enjoy and i will write some games, other math equation programs and so on! Thank you! S the? I will say that it always says no real answers and then the solution but other than that, absolutely amazing.

Reply 4 years ago. That is, unless the intention is do to part of the calculation in fixed point arithmetic. In such rare cases, split the expression in several lines.

Is that really the intention here? Because the results will be very different compared to floating point. This is likely caused by an IDE configured to use a certain style or give a default main - if so, you might want to look up how to set the IDE to cooperate with you instead of working against you. It's a major waste of time to have a code editor spit out code formatting which doesn't correspond with your preferred style. In practice a compiler might assume that UB never happens, and it might thus for instance remove the break statement entirely.

You need to handle the input error. If you want to use errno , your function could set errno in this case; but it would still be conventional to also signal success via the return value. In fact, your program will fail if somebody pipes input into it. Reading stdin into a temporary buffer in this way is fundamentally a bad idea.

Using f scanf would solve this issue. Result is an imprecise x1 or x2. You should know that double is the normal floating-point type, and float is half sized and should only be used where you really need to save the space. Your program is mostly dealing with reading input, which is not the problem you came to solve! A real utility program would take command line arguments, not prompt the user to type things. You should put the real work in a function, not directly in main. Then you can call it from testing code with built-in values that runs automatically.

Right now you have to re-type all your tests every time you re-test after a change! Put the input and output in separate functions too. Declare variables where you need them, not all at the top. This has been the standard in C for over twenty years now. Thank you all for your answers. I've learned a lot. In this stadium I think I'm done with this program unless there's some bug I don't know about may be, if I know myself.

Rewrote the original program to making it a running script instead of reading the result from stdin.