Thread: Please help on my Payroll system project

hi, im having trouble with my project. its a payroll system. i dont know how the name i inputted will be printed correctly. when i use scanf, it just print the first set of words. i learned that i should use strlen() but when i try to use it, it never let me to input then exit the program. what should i do? here's the code:

Code:

#include<stdio.h>
#include<conio.h>
#include<string.h>

#define p printf
#define s scanf
#define g gotoxy

main()
{

int select;
char name[30];
int n;

clrscr();

p("[1] 15th \n[2] Monthly \n\nSelect mode of payment: ");
s("%d", &select);

if(select==1)
{
clrscr();
p("15th \n\n");
p("Enter employee's name: ");
gets(name);
n=strlen(name);
p("Employee's Name: %s", name);
}

else if(select==2)
{
clrscr();
p("Monthly \n\n");
}

else
{
clrscr();
p("Invalid Selection");
}

getch();
}

i need this tomorrow morning so please help me, thank you

Originally Posted by Bayint Naung

fflush vs gets
Very common question.
Don't forget that gets is not safe function.
And what are these #define for??? I won't give any mark if I were to give mark.

define? its for those printf, scanf. so that i will just type p for printf and so on. so, i will not use gets? oh man...how can i do this

Ew, macro abuse. How hard it is to type out printf? Yeesh.

scanf leaves the newline in the input buffer. You need to flush out the input buffer with something like

Code:

int p;
while ( (p=getchar())!='\n' && p!=EOF);

Alternatively, use scanf or fgets (never gets) for everything to avoid the conflicts.

Originally Posted by KBriggs

Ew, macro abuse. How hard it is to type out printf? Yeesh.

scanf leaves the newline in the input buffer. You need to flush out the input buffer with something like

Code:

int p;
while ( (p=getchar())!='\n' && p!=EOF);

Alternatively, use scanf or fgets (never gets) for everything to avoid the conflicts.

so where should i put this? and what does it do?

Quick! Get me my shotgun, darling!

Got us some pesky defines hanging 'round, and I sure don't want to miss 'em.

Cute code, ain't - remember that.

Put it where the sun --- oh no, put it wherever you need to help clear the newline from the keyboard buffer.

If you read in something and it leaves crap in the input buffer, and you need to flush out the input buffer, then where, logically, would you put the code to do the flushing? ^_^

And I'm not saying another word until those defines have been nuked.