04-04-2004, 02:24 PM | #1 (permalink) |
Psycho
Location: i live in the state of denial
|
i'm teaching myself c....printf ( "sigh/n" )
i'm currently in the process of teaching myself the c language, and have succesfully written 12 extremely (and i mean EXTREMELY) low-level apps. as in, input a word and it spits it out backward. i've moved on to trying to manipulate numbers in c, starting with adding two integers. when i attempt to compile the prog
#include <studio.h> int main() { int integer1, integer2, sum; printf( "Enter the first number that this program will add/n" ); scanf( "%d", &integer1 ); printf( "Enter the second number to the program/n" ); scanf( "%d", &integer2 ); sum = integer1 + integer2; printf( "sum is %d\n", sum ); /*what's the fucking problem here??*/ return 0; } i get a debugging error saying C:\Program Files\Miracle C\examples\adding.c: line 12: wrong # args in function call 'printf( "sum is %d\n", sum )' aborting compile i'm using miracle c 3.2 on windows xp, and the code is almost taken straight from a text (Deitel and Deitel's "How to Program C: Third Edition") btw, please excuse the profanity in the code, after rewriting it four times i got a tad frustrated. i can't figure out why it's telling me that the # of arguments is off, i checked all the references i could find and can't find anything that helps. what's the problem with line 12? |
04-04-2004, 03:24 PM | #6 (permalink) |
I am Winter Born
Location: Alexandria, VA
|
Well, the first problem is that it's "stdio.h" not "studio.h"
The second problem is that you want \n instead of /n in order to get newline. And after that, the code worked just fine when compiled with gcc for me.
__________________
Eat antimatter, Posleen-boy! |
04-04-2004, 04:02 PM | #7 (permalink) |
Location: Waterloo, Ontario
|
Except for some obvious typos, there's nothing wrong with your program. If you had actually tried to include studio.h then that would have been the only error your compiler would have reported. A /n would not stop your compile, so that's not your problem, either. Either you're mistyped your program while trying to describe it to us or your program compiles...
Oh, you might want to consider using the [code] blocks for displaying your code... And, just so you know, low-level programming doesn't mean what you think it means. You can describe your programs as being simple or elementary, but a low-level program is one that works very closely with the hardware, like an operating system. A high-level program is one that is no where near any hardware, like... Well, like most software (these days). MircX, WinZip, or whatever. A low-level program can be very complex or very simple, as can a high-level one... |
04-05-2004, 07:22 AM | #12 (permalink) |
I am Winter Born
Location: Alexandria, VA
|
Yea - I'm also surprised that the compiler didn't complain. gcc instantly said it couldn't be found.
If you want to use gcc, I'd say download cygwin for your Windows computer and write the programs in whatever (Vim, Notepad, etc.), then open up a Cygwin shell, go to the right directory, and compile with gcc.
__________________
Eat antimatter, Posleen-boy! |
Tags |
cprintf, sigh or n, teaching |
|
|