Click here to Skip to main content
15,889,767 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more:
C
#include<stdio.h>
#include<math.h>
int main()
{

    //to find the armstrong number in c language!!

    int count=0,temp,digit,t,n,original,rem,sum=0;
    printf("\nenter the number: ");
    scanf("%d",&n);
    t=n;temp=n;original=n;

    while(t!=0)
    {
        digit=t%10;
        count=count+1;
        t=t/10;
    }
    while(temp!=0)
    {
        rem=temp%10;
        sum=sum+pow(rem,count);
        temp=temp/10;
    }
    if(original==sum)
    {
        printf("\nArmstrong number!!");
    }
    else
    {
        printf("\nnot Armstrong number!!");
    }
    return 0;
}


What I have tried:

here is a c program to find the Armstrong number and it is showing different and in the different compiler. I want anyone to tell me the correct code and what is the mistake in this code with the least minimum correction and if you will give the and then it would he very helpful to me as well . I want to want to get the ans eg 153 370 to be working with Armstrong number thanks.
Posted
Updated 10-Apr-21 22:25pm
v2

Quote:
it is showing different and in the different compiler.

This is just not a sentence, can you elaborate ?
As far as I can seen your code is working.

Your code do not behave the way you expect, or you don't understand why !

There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.

Debugger - Wikipedia, the free encyclopedia[^]

Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]
Basic Debugging with Visual Studio 2010 - YouTube[^]

1.11 — Debugging your program (stepping and breakpoints) | Learn C++[^]

The debugger is here to only show you what your code is doing and your task is to compare with what it should do.
 
Share this answer
 
v2
Getting your code to run at all does not mean it 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!
 
Share this answer
 
Comments
vishal kumawat 10-Apr-21 17:01pm    
@OriginalGriff thanks for the advice. :)
Removed some of the unnecessary/redundant code

#include<stdio.h>
#include<math.h>

int main()
{
	int temp = 0;
	int original = 0;
	int rem = 0;
	int sum = 0;
	int count = 0;

	printf("\nenter the number: ");

	scanf("%d", &temp);

	original = temp;

	count = (temp == 0) ? 1 : (log10(temp) + 1);

	while (temp > 0)
	{
		rem = temp % 10;
		sum = sum + (pow(rem, count));
		temp = temp / 10;
	}

	if (original == sum)
	{
		printf("\nArmstrong number!!");
	}
	else
	{
		printf("\nnot Armstrong number!!");
	}

	return 0;
}
 
Share this answer
 
v2
Comments
vishal kumawat 10-Apr-21 16:57pm    
@Tony Hill its correct for 3 digits only but I need a universal solution
Dave Kreskowiak 10-Apr-21 22:50pm    
Oh, you're making the mistake of thinking someone is going to do your work for you.

No, that's not how this works. We'll help you debug your own code, but that's as far as this goes.
Tony Hill 11-Apr-21 5:33am    
I have modified the code in my example, next time you ask a question try and make the intent more clear so others can understand your problem.

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900