Should look at C

Seem as got it: I should look at C code for particular numbers.
But it should be nice to have typical exit codes and their probable explanations as a document to read or look up.

Comment on Should look at C

Replies are listed 'Best First'.
Re: Should look at C by cdarke (Prior) on Jan 20, 2010 at 13:28 UTC
Here's a quick and dirty way of translating exit codes to their C error strings: `local $! = 512 >> 8; print "$!\n";` [download] BUT you should be careful! Not everyone uses the C runtime-library error numbers. Exit codes are application specific, they should be listed in the application documentation.	[reply] [d/l]
Re: Should look at C by Corion (Patriarch) on Jan 20, 2010 at 12:08 UTC
Your OS should have these. They are specific to each OS.	[reply]