first_number = number / 10 ;
second_number = number % 10 ;
switch (first_number) {
case 9: printf ("ninety"); break;
case 8: printf ("eighty"); break;
case 7: printf ("seventy"); break;
case 6: printf ("sixty"); break;
case 5: printf ("fifty"); break;
case 4: printf ("forty"); break;
case 3: printf ("thirty"); break;
case 2: printf ("twenty"); break;
}
if(first_number != 0 && second_number != 0) {
printf("-");
}
switch (second_number) {
case 9: printf ("nine"); break;
case 8: printf ("eight"); break;
case 7: printf ("seven"); break;
case 6: printf ("six"); break;
case 5: printf ("five"); break;
case 4: printf ("four"); break;
case 3: printf ("three"); break;
case 2: printf ("two"); break;
case 1: printf ("one"); break;
}
printf("\n");Scott-Deans-MacBook-Pro:documents scottdean$ gcc ~/documents/number2number.c
/Users/scottdean/documents/number2number.c: In function main:
/Users/scottdean/documents/number2number.c:74: error: expected ) before ! token first_number = number / 10 ;
second_number = number % 10 ;
switch (first_number) {
case 9: printf ("ninety"); break;
case 8: printf ("eighty"); break;
case 7: printf ("seventy"); break;
case 6: printf ("sixty"); break;
case 5: printf ("fifty"); break;
case 4: printf ("forty"); break;
case 3: printf ("thirty"); break;
case 2: printf ("twenty"); break;
}
if(first_number ! = 0 && second_number ! = 0) {
printf ("-") ;
}
switch (second_number) {
case 9: printf ("nine"); break;
case 8: printf ("eight"); break;
case 7: printf ("seven"); break;
case 6: printf ("six"); break;
case 5: printf ("five"); break;
case 4: printf ("four"); break;
case 3: printf ("three"); break;
case 2: printf ("two"); break;
case 1: printf ("one"); break;
}
printf ("\n") ;I agree with you chown33. I also know of other expressions that some C programmers write routinely, although those expressions don't look boolean. Professor Allan Nash, for example, would write "while (fgets(line, sizeof(line), input)" instead of while "(fgets(line, sizeof(line), input) != NULL)." I understand both expressions. But if your computer checks the first expression with a program called "splint," not "lint," the machine will complain that "while (fgets(line, sizeof(line), input)" is nonboolean. There aren't an truth-values at runtime, and a C programmer should see a program the way the computer sees it when it compiles that program. My question about "(tens && ones)" was about style and about what seems intuitive, not about how the computer saw that expression.
Thanks, Lee. Sadly, I've misinterpreted most of what people me in this thread today. I think hyper-analytically. But sometimes my feelings and my impulsiveness cloud my judgment. I learn best by hearing.
Darn, I'm cursing myself for that! No I didn't realize the spacing was important, I just figured the compiler read from left to right associative, and there is nothing in between. I like to space everything for readability, but now I see that sometimes that can't be done with everything.
if ( ones != 0 && tens != 0 ) {...if(ones != 0 && tens != 0){...Maybe someone needs to revise some programming languages to improve their readability. In Prolog, a semicolon means "or," and "\+" means "can't prove." I've read some programs, or maybe some pseudocode," where a right-arrow was an assignment operator. In what I'd read, "x -> 1" meant what "x = 1" means in C. For years, I read textbooks full of pseudocode where "<-" was an assignment operator. "X <- Y" made sense to me, but "X -> Y" confused me.
I've seen that notation in processor manuals. I usually read it as "copied to". Sometimes the source is parenthesized: (X) -> Y, read as "contents of X copied to Y", where X and Y are register names.
Darn, I'm cursing myself for that! No I didn't realize the spacing was important, I just figured the compiler read from left to right associative, and there is nothing in between. I like to space everything for readability, but now I see that sometimes that can't be done with everything.
(a != b)!(a == b)!(a = b)Maybe I'm qualified because I know how to program reasonably well. But I'm not a Mac expert.
>Thanks. Now both symbols make sense to me. There's still something I'll never understand, though. In Cobol, the word "move" means "copy" and the word "copy" means "include."
Aha! Now I know who can teach me Shakespeare.
Meanwhile, each time I post to this thread, Lee's avitar appears on my screen before the post does. It's as though I keep seeing the ghost of Hamlet's father. Years ago, I tutored a student who asked me to help him debug his COBOL program that made the computer repeat a report's last line. After I stared at the program for 10 or 15 minutes, I discovered that he called a paragraph recursively when the language supposedly doesn't support recursion. I explained the problem and told him that he needed to revise the recursive paragraph. He replied he didn't want to do that. Thank God I didn't mention that we were using an OS that let you edit output in the print queue.This reminded me that when the C++ language was new someone suggested Object-Oriented COBOL and that it be named "ADD 1 TO COBOL GIVING COBOL."
FWIW Beautiful Code is part of today's eBook promotion at O'Reilly along with other "Theory in Practice" books. http://oreilly.com/store/dd-theory.html
