I want enter two values, C problem

Question

1.00/5 (6 votes)

See more:

The program asks for bugs like this:

2

14 1

14 1

14.85

But I don't want input like this.

2

14 1

14.85

What I have tried:

#include <stdio.h>

int main() {
    int n, i, count = 0;
    float price, total = 0, discount = 0, max_discount = 0;

    scanf("%d", &n);

    for(i = 0; i < n; i++) {
        scanf("%f", &price);
        total += price;
    }

    if(n == 1 || n == 2) {
        if(total < 20)
            discount = 0;
        else
            discount = total * 0.1;
    } else {
        if(total < 20)
            discount = total * 0.07;
        else {
            discount = total * 0.15;
            if(discount > total * 0.5)
                discount = total * 0.5;
        }
    }

    for(i = 0; i < n; i++) {
        scanf("%f", &price);
        if(price > 7)
            discount += total * 0.01;
    }

    printf("%.2f\n", total - discount);

    return 0;
}

Posted 3-May-23 10:35am

mohammedhaj6

Updated 3-May-23 18:56pm

Add a Solution

Comments

Rick York 3-May-23 17:14pm

Do you have a question?

Also - your program deals with prices and discounts. What do bugs have to do with it?

Richard MacCutchan 4-May-23 7:15am

Why are you trying to enter two numbers (14 1) when your code only accepts a single value?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2023-05-03T18:56:00

This is not a good question - we cannot work out from that little what you are trying to do.
Remember that we can't see your screen, access your HDD, or read your mind - we only get exactly what you type to work with - we get no other context for your project.
Imagine this: you go for a drive in the country, but you have a problem with the car. You call the garage, say "it broke" and turn off your phone. How long will you be waiting before the garage arrives with the right bits and tools to fix the car given they don't know what make or model it is, who you are, what happened when it all went wrong, or even where you are?

That's what you've done here. So stop typing as little as possible and try explaining things to people who have no way to access your project!

So all I can do is be generic, and say that compiling successfully does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:

Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16

Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:

C

int Double(int value)
   {
   return value * value;
   }

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!