07-19-2012, 09:43 PM
Hi,
Whenever compiling any ZX BASIC program that uses the latest BIFROST* interface library, it will always produce the following warnings:
In general, these warnings are very useful to notify the user about possible problems on the code. But in the cases when they were already validated (such as above where FASTCALL is used intentionally for performance reasons), they become a disadvantage: the user will always see warnings in every compilation and will soon start to ignore them completely, thus not paying attention anymore to new warnings that may appear about real problems in his/her own code.
I suggest a new directive to allow ignoring such warnings inside an specific library. The idea is that a library file could use something like this:
Makes sense?
Whenever compiling any ZX BASIC program that uses the latest BIFROST* interface library, it will always produce the following warnings:
Code:
bifrost.bas:92: warning: FUNCTION 'BIFROSTfindAttr' declared as FASTCALL with 2 parameters
bifrost.bas:177: warning: SUB 'BIFROSTshowTile' declared as FASTCALL with 3 parameters
bifrost.bas:201: warning: SUB 'BIFROSTshowTilePos' declared as FASTCALL with 2 parameters
bifrost.bas:231: warning: SUB 'BIFROSTfillTileAttr' declared as FASTCALL with 3 parametersI suggest a new directive to allow ignoring such warnings inside an specific library. The idea is that a library file could use something like this:
Code:
#pragma push(fastcall_warning)
#pragma fastcall_warning = false
...
#pragma pop(fastcall_warning)
