XC8 V2.00和可编程问题

老实说：声明ISR外部是无稽之谈，一直以来都是：你不能调用它们，而不使用@外部声明是不太有用的。为什么不适当设置“警告级别”呢？（编译器选项中的“某处”）或学习如何编写不被十二个线程发出警告的代码？（根据我的经验，一些警告不能被消除。但是大多数都会消失。
                    
                    
               
                                                                                      以下为原文

                                                                            Honestly: declaring ISRs external is nonsense and has always been: you cannot call them.
And not having the @ for external declarations is hardly more useful.
--MSGDISABLE ? Why not set the "warning level" appropriately ? ("somewhere" in the compiler options)
Or learn how to write code that doesn't throw warnings by the dozen? (OK - according to my experience, some warnings cannot be eliminated. But the majority will vanish with proper coding.)

？？？？我在一个单独的模块中具有IRS功能，这些函数在调用它们的另一个.c文件中被声明为外部（这是因为声明是框架的预定义模块的一部分，而ISR是用户可定义的）。你怎么会想到那些功能不能被这样称呼？@不是用于外部变量，而是用于在HEX分析的相同地址中总是找到的常量。我可以正确地编写代码，比您能想到的要好得多，但是对于每个和在库中定义但未被调用的所有函数发出警告只是简单的。nnink，这是相对于任何指针可能没有目标的事实的警告（即使你写指针= ANABOXTETEL地址，然后*指针＝0），警告你一些移位是不合适的（即使它们在逻辑观点下是正确的），尽管编译器用一个固定的和不变的算术角度来看待它们，或者那些TAT告诉我，零移不产生代码（如果我使用定义或枚举或索引作为移位值，我不检查移位的零值，以避免无用的警告，是吗？）删除那些恼人的警告并不意味着我也想删除其他可能在同一个级别上有意义的警告。BTW：在全局选项的附加选项中使用-MSGDABLE选项确实可以抑制警告，但是编译器哀叹该选项不被重新编码。Neal:同样的，如果选项是大写的，OpTunUnDebug也不被识别（虽然我没有测试IRQ是否被正确地忽略或忽略）如果选项是小写的，同样，最后但不是最不重要的一点是，改变项目配置需要很多，有时会完全冻结IDE。
                    
                    
               
                                                                                      以下为原文

                                                                            ???
I have IRS functions in a separate module and those functions are extern declared in another .c file that calls them (that's because the declaration are part of a predefined module of a framework while the ISR are user definable). How do you come to the idea that those functions cannot be called that way?
@ was not used for external variables, but for constants that must be always found at the same address for HEX analysis.
I can properly write code much better than you can think, but having warning that is issued for each and all functions that are defined in a library but are not called is simply annoying, as is the warning relative to the fact that whatever pointer may have no target (even if you write pointer = anAbsoluteAddress and then *pointer = 0) as is the one that warns you that some shiftings are not appropriate (even though they are correct under a logical point of view, though the compiler sees them with a fixed and unchangeable arithmetic point of view) or those tat tells me that shifting by zero produces no code (if I use defines or enums or indexes as shifting value I do not check for shiftings by zero values to avoid the useless warning, do you?).
Removing those annoying warning does not mean I want to remove also the other ones at the same level that may have a meaning.
 
BTW: the warning are indeed suppressed with the use of the --MSGDISABLE option in Additional options of Global options, but the compiler laments that the option is not recognized:
::: warning: (2044) unrecognized option "--msgdisable=362,520,1498"
Same if the option is uppercase.
 
Also the option UNDEFINTS is not recognized (though I have not tested if the IRQs are correctly ignored or not)
::: warning: (2044) unrecognized option "--UNDEFINTS=ignore"
Same if the option is lowercase.
 
Last but not least, changing the project configuration takes a lot and sometimes freezes completely the IDE.