That being said, you have a few problems and things you could do to clean it up a bit: Normally we don't want to go around pretending to be a compiler or a QA department, debugging code for somebody, we prefer them to indicate their problem and what they've tried, and we'll help them the rest of the way.

Writing small amounts of code and testing as you go is very helpful here too. Break that solution down into it's parts, and put each part in it's own module/function to isolate the problems. Make sure you understand the problem well, then devise a good solution on paper. Fix all errors and warnings before running your code.Īctually, your first line of defense is probably a good design and programming process. That being said, your first line of defense against bugs is to compile with the warnings turned all the way up. You should work on your testing abilities, so you can check for bugs/problems yourself. Printf ('Dealer has %d! Congratulations!',dealer)

Printf ('Dealer has %d!You lost!',dealer) Printf ('Dealer stands at all (hard or soft) 17's! ')

C blackjack simulation