Thread: Useful program

Here is a little program I made that displays ascii key codes. It can display the full listing, a designated number of codes, or a single code. Great for when you need to know a code for something real fast. If you think I should make any changes to it tell me.

I have neither the time nor the inclination to disassemble your program and make sure that it's safe. The program doesn't sound that enticing either, so you'll need to post some code to attract my interest.

Why would I give you all something that would harm your PC? Here is the source code but it's nothing special.

We distrust everyone. Plus no one learns from the executable

Edit: Speaking of learning:
Things I see wrong without even thinking

Code:

#include <conio.h>

Non standard header

Code:

void main()

Main returns an int

Code:

printf("%c %i\n",c,c);

1) Not every machine uses ASCII so this won't print the ASCII table correctly on all machines
2) c is an int, you are passing an int when you should be passing a char for the first type specifier

Code:

gets(code);

THERE IS NO EXCUSE FOR gets() EVER!


See this is why we ask for the source. Had my computer ran this it would have kicked me.

Did I ask for your comments on my code? No. Did I say it was flawless 150% correct code? No! You don't need include files for the program to work, so it doesn't matter what header you use. If it does't work right for you then you can't use it. Unless you are on purpose going to overflow gets with jargon then it doesn't matter to me what input function you use. I made it for convenience so if you don't like it, don't use it. Very simple. Go look your codes up in a book if you hate it so much.

I use it all the time and it does it's job well. In my opinion it is very immature for someone to immediately pick at every little thing in someone's code. Go make your own ascii viewer.

Maybe you are right, but I don't see anything wrong with void main and including the conio.h header. I'll try to change the gets.

Originally Posted by Kleid-0

I think all noobs shouldn't follow this rule, because a lot of rules makes programming really distasteful. Don't do THIS, do THAT, and then I get confused and I get depressed! Sometimes people who say: "Don't do this!" that don't even supply the solution for what to use without it. And that's ok, but it gets intense! It's hard being a learner :'(

i honestly appreciate people pointing out my mistakes and potential mistakes and why they are mistakes..i learn twice as much from one mistake than reading one chapter in "teach yourself c in16 seconds" or whatever my chosen text shall be....however, if someone does point out a mistake, but it's unrelated to my original problem and they offer no help with the original problem (or saying they don't know), then it does seem like nit picking...i understand though...but most noobs probably do not