I just compile the calc snippet with gcc (gcc version 4.0.0 20041026), and it simply gives the first number of the expression as the answer. I thought get_token() might not be appropriately advancing, but it will grab an operator followed by a number. It can operate correctly by placing each term of the expression in a separate round of input. However, * and / operators (as well as parens) are basically ignored.

Below is a sample usage cycle (as well as the gcc warnings, though you can ignore the returntype ... if you've not used gcc, it simply warns when you're not sending a return value to the OS as per POSIX, since the $? of ccalc is then highly unpredictable. (Portability note: int main() { return 0; } helps programs play nicely with standards-compliant OS'es.) Hope this helps, as I don't have time to debug it at present. Cheers!

I've got good news, and I've got bad news:
The universe is merely a figment of my imagination.
Now are you ready for the bad news?

Sorry, "compile" == "compiled" . . .

I've got good news, and I've got bad news:
The universe is merely a figment of my imagination.
Now are you ready for the bad news?

if python is not installed {
install python
}
open command/terminal
execute python
print (enter calculations)

Just thought I'd throw that out there

Or, on a *nix system, one might write a shell function to call bc. Then

$> calc "expression"

would yield fantabulous results . . .

I've got good news, and I've got bad news:
The universe is merely a figment of my imagination.
Now are you ready for the bad news?