Thread: Implement with atoi() to convert ASCII to integer.

Code:

#include <stdio.h>#include <stdlib.h>
#include <math.h>
#include "calc.h"
#define MAXOP 128
int main(int argc, char *argv[]){
    
int type;
double op2;
char s[MAXOP];
    
while ((type = getop(s)) != EOF) {
    switch(type) {
        case NUMBER:
           push(atof(s));
           break;
        case '+':
            push(pop() + pop());
            break;
        case '-':
            op2 = pop();
            push(pop() - op2);
            break;
        case '*':
            push(pop() * pop());
            break;
        case '/':
            op2 = pop();
            if (op2 != 0.0)
                push(pop() / op2);
            else {
                printf("error : zero divisor\n");
            }
            break; 
        case '|': 
            push (pop() | pop()); 
            break; 
        case '&': 
            push (pop() & pop()); 
            break; 
        case '^': 
        case '~': 
        case '=': 
            
            if (pop() == pop())
                push(1); 
            else 
                push(0); 
            break; 
        case '>':
            op2 = pop();
            if (pop() > op2)
                push (1); 
            else 
                push(0); 
            break; 
         case '<':
            op2 = pop();
            if(pop() < op2)
                push(1); 
            else 
                push(0); 
            break;

use atoi() to convert ASCII to integer. Additionally, you add
functionality to the calculator by implementing the following bitwise operations.

I did include bitwise operations but I'm struggling how to include atoi() instead of atof() that the program has itself.

Thanks in advance

Presumably you already did the "backspace over the f and type an i" bit. And then you're set! (At least as far as the syntax is concerned; you can see push(1) and push(0) sprinkled throughout your code already, so your stack can handle plain integers.)

Now of course, if you try typing a number with a decimal point in it, everything will fail horribly, so try not to do that. If you need to handle both, then you'll need to be more careful with your parsing to be able to distinguish the different cases of "50" and "50.5".