Okay, here goes:
Code:
// Constants required by programme
//----none----
You don't need to say that the program doesn't use named constants. Their absence makes that point obvious.
Code:
// Function Prototypes -- alphabetical order
Alphabetical order is nice, but order of importance is better. Or order of dependence. For example, if foo calls bar, and baz is a helper for both you could do this:
Code:
void baz ( void );
void bar ( void );
void foo ( void );
Or take the opposite route and say that foo is the highest level function and bar and baz are mere helpers, so they aren't as important:
Code:
void foo ( void );
void bar ( void );
void baz ( void );
Alphabetical order rarely makes the structure of the program clear. Coupled with good naming schemes, one of the above or something else would.
>void decideOutcome(int*,int*,int*,int*,int*,int*,int*);
Most of the time, that many parameters means your design needs work. Since the first five variables are slots, you can easily use an array instead. It's also a good idea to use parameter names even in your prototypes. Even though they aren't required, their presence does make understanding the code easier. Of course, this assumes well chosen names.
>/* Variable Table
I can't say as this is a good idea. It might be better to declare your variables on a single line followed by a descriptive comment instead.
>int slot1,slot2,slot3,slot4,slot5;
This would be easier to work with as an array.
>//declaring floats (real values)
I think we all know what floats are, perhaps something more descriptive as to the purpose instead of the mechanism.
>//repitition structure to repeat tasks if certain are true (do.while loop).
Once again, don't bother with mechanism. Even if you made the comment
Code:
// Keep taking the user's money until they're broke.
it would be better than saying what is obvious, that here there be loops.
>void decideOutcome(int* slot1,int* slot2,int* slot3,int* slot4,int* slot5,int* win,int* lose)
Lose and win being pointers I can understand, but you don't write to any of the slots in this function. Making them pointers just clutters the syntax.
>srand (time (0));
This would better placed in main so that you only end up calling it once.
>scanf ("%d",choice);
Always check to make sure that the user isn't stupid. They too often are:
Code:
if ( scanf ( "%d", choice ) != 1 ) {
/* Something wrong, bail */
return 2;
}
/* Band-Aid for scanf, replaces fflush(stdin) */
while ( getchar() != '\n' )
;
>scanf("%f", bet);
See above.
>fflush (stdin);
See above above.
>void programmeInfo(void)
You have an eight line comment to describe a three line function...
There isn't anything really bad about your program, and nothing that a good perusal of K&R won't cure.