lassik
/
upscheme
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
upscheme/c/error_dmc.h

18 lines
503 B
C
Raw Normal View History

Reorganize error functions and includes These functions are complicated because they need to be marked "noreturn" for the compiler. There are several fundamentally incompatible ways of doing that. Since we have only a few "noreturn" functions, let's just list all of those in one header file of which there is a completely different version for each compiler.
2019-08-21 15:06:13 -04:00
extern void DivideByZeroError(void);
#pragma noreturn(DivideByZeroError)
Add const to many utility functions
2019-08-25 15:11:00 -04:00
extern void lerrorf(value_t e, const char *format, ...);
Reorganize error functions and includes These functions are complicated because they need to be marked "noreturn" for the compiler. There are several fundamentally incompatible ways of doing that. Since we have only a few "noreturn" functions, let's just list all of those in one header file of which there is a completely different version for each compiler.
2019-08-21 15:06:13 -04:00
#pragma noreturn(lerrorf)
extern void lerror(value_t e, const char *msg);
#pragma noreturn(lerror)
extern void fl_raise(value_t e);
#pragma noreturn(fl_raise)
Add const to many utility functions
2019-08-25 15:11:00 -04:00
extern void type_error(const char *fname, const char *expected, value_t got);
Reorganize error functions and includes These functions are complicated because they need to be marked "noreturn" for the compiler. There are several fundamentally incompatible ways of doing that. Since we have only a few "noreturn" functions, let's just list all of those in one header file of which there is a completely different version for each compiler.
2019-08-21 15:06:13 -04:00
#pragma noreturn(type_error)
Add const to many utility functions
2019-08-25 15:11:00 -04:00
extern void bounds_error(const char *fname, value_t arr, value_t ind);
Reorganize error functions and includes These functions are complicated because they need to be marked "noreturn" for the compiler. There are several fundamentally incompatible ways of doing that. Since we have only a few "noreturn" functions, let's just list all of those in one header file of which there is a completely different version for each compiler.
2019-08-21 15:06:13 -04:00
#pragma noreturn(bounds_error)