04-21-2005, 05:56 PM
04-21-2005, 06:40 PM
I would think the errors are according to the OS you're coding under :-)....
I built a list of Windows errors on my website
http://www.ascii-world.com/tutors/window...sages.html
I built a list of Windows errors on my website
http://www.ascii-world.com/tutors/window...sages.html
04-21-2005, 09:25 PM
The runtime errors list is pretty short, taken from libfb_error.c:
OK = 0, ILLEGALFUNCTIONCALL = 1 and so on..
Code:
static const char *error_msg[] = {
"", /* FB_RTERROR_OK */
"illegal function call", /* FB_RTERROR_ILLEGALFUNCTIONCALL */
"file not found", /* FB_RTERROR_FILENOTFOUND */
"file I/O error", /* FB_RTERROR_FILEIO */
"out of memory", /* FB_RTERROR_OUTOFMEM */
"illegal resume" /* FB_RTERROR_ILLEGALRESUME */
};
OK = 0, ILLEGALFUNCTIONCALL = 1 and so on..
04-22-2005, 09:58 AM
would it be possible to add an "out of bounds" error for arrays?
04-23-2005, 09:54 PM
Only when that gets added, it will have to be added inline etc.. adding proper debugging support is the next priority..