Click here to Skip to main content
15,898,371 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
Operation 1: Find A raised to the power of B.
Operation 2: Find A raised to the power of B, then XOR of the result with the number C.
Operation 3: Find A raised to the power of B, then divide the result by C and print the remainder.

Input:
First line contains number of testcases T. For each testcase, there will be single line containing  three positive integers A, B and C.

Output:
For each testcase, print the required answer.


What I have tried:

#include<bits/stdc++.h>
using namespace std;
void operations(int a, int b, int c);
int main(){
    
    int testcase;
    cin >> testcase;
    
    while(testcase-- > 0){
        
        int a, b, c;
        
        cin >> a >> b >> c;
        
        operations(a, b, c);
        
    }
}

void operations(int a, int b, int c){
    
    int d=pow(a,b);
    cout<<d<<endl;
    int e=d^c;
    cout<<e<<endl;
    int f=d%c;
    cout<<f<<endl;
}
Posted
Updated 25-Nov-18 23:41pm
v2
Comments
CPallini 26-Nov-18 4:31am    
What is the input? What is the expected output?
Prateek Krishna 26-Nov-18 4:36am    
Constratints:
1 <= T <= 10
1 <= A <= 20
0 <= B <= 10
1 <= C <= 100

Example:
Input:
1
5 2 3

Output:
25
26
1
Patrice T 26-Nov-18 4:56am    
what is actual output ?
Richard MacCutchan 26-Nov-18 4:53am    
What is the problem?
Prateek Krishna 26-Nov-18 4:57am    
it is showing wrong answer

One problem in your code is the chosen data type: A raised to the power of B for A=10, B=20 does NOT fit in an int data type (see Fundamental types - cppreference.com[^]). you should use a long long datatype. The following program
C++
#include <iostream>
#include <cmath>
using namespace std;

using ull = unsigned long long;

void operations_ull(ull a, ull b, ull c){

    ull d =pow(a,b);
    cout << d << endl;
    ull e = d^c;
    cout << e << endl;
    ull f=d%c;
    cout << f << endl;
}

void operations_int(int a, int b, int c){

    int d =pow(a,b);
    cout << d << endl;
    int e = d^c;
    cout << e << endl;
    int f=d%c;
    cout << f << endl;
}

int main()
{
  int A = 20;
  int B = 10;
  int C = 99;
  printf("int data type\n");
  operations_int(A,B,C);
  printf("unsigned long long data type\n");
  operations_ull(A,B,C);
}

outputs
int data type
-2147483648
-2147483549
-2
unsigned long long data type
10240000000000
10240000000099
34
 
Share this answer
 
Compiling 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!
 
Share this answer
 
Do yourself a favour, and look at your constraints:
Constratints:
1 <= T <= 10
1 <= A <= 20
0 <= B <= 10
1 <= C <= 100

your first task is to raise A to the power of B, so assuming a test on your max constraints that's 20^10 : 1.024e+13
Does that fit in an integer?
 
Share this answer
 
v2

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