d0p1/tcc-stupidos
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tcc-stupidos/tests/tests2/117_builtins.expect

5 lines
157 B
Text
Raw Normal View History

tests2: rework 117..119 to follow our conventions Please respect some conventions: - tests2 filenames don't end with '..._test' - tests2 tests are meant to produce some output - the output should be somehow informative, not just "error" or "dummy". Because other people would want to know where it fails if it does. - tests2 tests should work with both GCC and TCC, except if there are specifc reasons (like testing tcc-only feature such as bounds checking) - tests2 tests should never crash or abort. Because that would cause gui dialogs to pop up on windows, and because other people would not know where it fails if it does. - tests2 tests should be somehow specific, in general. (rather than just collections of random stuff) - in general, do not use 'long' if you mean 'larger than int' Because it isn't on many platforms. - use four (4) spaces for block indention. Do not insert tab characters in files if possible. Also: - tccgen.c:gen_cast() simplify last fix.
2020-07-08 02:37:04 +00:00
BOUNDS OFF:
Add strncat and strrchr to bounds checking
2022-11-25 06:31:32 +00:00
1:1 2:1 3:1 4:1 5:1 6:1 7:1 8:1 9:1 10:1 11:1 12:1 13:1 14:1 15:1
tests2: rework 117..119 to follow our conventions Please respect some conventions: - tests2 filenames don't end with '..._test' - tests2 tests are meant to produce some output - the output should be somehow informative, not just "error" or "dummy". Because other people would want to know where it fails if it does. - tests2 tests should work with both GCC and TCC, except if there are specifc reasons (like testing tcc-only feature such as bounds checking) - tests2 tests should never crash or abort. Because that would cause gui dialogs to pop up on windows, and because other people would not know where it fails if it does. - tests2 tests should be somehow specific, in general. (rather than just collections of random stuff) - in general, do not use 'long' if you mean 'larger than int' Because it isn't on many platforms. - use four (4) spaces for block indention. Do not insert tab characters in files if possible. Also: - tccgen.c:gen_cast() simplify last fix.
2020-07-08 02:37:04 +00:00
BOUNDS ON:
Add strncat and strrchr to bounds checking
2022-11-25 06:31:32 +00:00
1:1 2:1 3:1 4:1 5:1 6:1 7:1 8:1 9:1 10:1 11:1 12:1 13:1 14:1 15:1
Reference in a new issue Copy permalink