C Exercises: Check if a number is Harshad Number or not

Last update on May 27 2022 12:18:12 (UTC/GMT +8 hours)

C Numbers: Exercise-17 with Solution

Write a program in C to check if a number is Harshad Number or not.

Test Data
Input a number: 9

Sample Solution:

C Code:

# include <stdio.h>
# include <stdlib.h>
# include <stdbool.h>


bool chkHarshad(int n)
{
    int s = 0;
	int tmp;
    for (tmp=n; tmp>0; tmp /= 10)
        s += tmp % 10;
    return (n%s == 0);
}
int main()
{
    int hdno;
	printf("\n\n Check whether a number is Harshad Number or not: \n");
	printf(" ---------------------------------------------------\n");
	printf(" Input a number: ");
	scanf("%d",&hdno);
 
     if( chkHarshad(hdno))
	printf(" The given number is a Harshad Number.\n");
    else
	printf(" The given number is not a Harshad Number.\n");
    return 0;
}

Sample Output:

 Input a number: 9                                                                                            
 The given number is a Harshad Number.

Pictorial Presentation:

C programming: Check if a number is Harshad Number or not.

Flowchart:

C Programming Code Editor:

Contribute your code and comments through Disqus.

Previous: Write a program in C to find Disarium numbers between 1 to 1000.
Next: Write a program in C to find Harshad Number between 1 to 100.

What is the difficulty level of this exercise?

Test your Programming skills with w3resource's quiz.

C Programming: Tips of the Day

Static variable inside of a function in C

The scope of variable is where the variable name can be seen. Here, x is visible only inside function foo().

The lifetime of a variable is the period over which it exists. If x were defined without the keyword static, the lifetime would be from the entry into foo() to the return from foo(); so it would be re-initialized to 5 on every call.

The keyword static acts to extend the lifetime of a variable to the lifetime of the programme; e.g. initialization occurs once and once only and then the variable retains its value - whatever it has come to be - over all future calls to foo().

Ref : https://bit.ly/3fOq7XP