错误：for循环初始声明仅允许在C99模式下解决

XC16是一个“C89”编译器，有几个C99扩展。我认为XC16根本没有C99模式。这是一个尴尬的说法，“这是一个C99的特点，我根本不支持”。



      以下为原文

    XC16 is a "C89" compiler, with a few C99 extensions.
I don't think there is a C99 mode in XC16 at all. That's an awkward way of saying "that is a C99 feature that I don't support at all".
 

ProjtualProjys:编译器OpthCopySCAN不记得该选项的确切名称，但是单击一位应该会成功。



      以下为原文

    project properties | compiler options
Cannot recall the exact name of the option but clicking a bit should result in success.

事实上，我从来没有觉得有必要这样做。”“本地化变量”，是的，哦…



      以下为原文

    I actually never felt the need for that feature. "localizing variables", yeah, oh well...

你确定？在最新的XC16用户指南中没有提到它。



      以下为原文

   
Are you sure? There's no mention of it in the latest XC16 User Guide.
 

你确定？在最新的XC16用户指南中没有提到它。真的，我也找不到。



      以下为原文

   
Are you sure? There's no mention of it in the latest XC16 User Guide.
 




True, I couldn't find it either.

AHEM，为什么你没有读编译器输出的下一行？（xC16 v1.31）./main .c:1368：2：“循环”初始声明仅允许在C99模式中使用./main .c:1368：2：注意：使用选项-STD= C99或-STD= GNU99编译您的代码添加，该选项按预期工作。但是，这会改变更多，也就是说，您将得到不同的警告。R等…



      以下为原文

    Ahem, why did'nt you read the next line the compiler outputs ?  (XC16 v1.31)
 
../main.c:1368:2: error: 'for' loop initial declarations are only allowed in C99 mode
../main.c:1368:2: note: use option -std=c99 or -std=gnu99 to compile your code
 
Adding this option works as expected.
However this changes more than this, i.e. you then will get different warnings for other stuff etc ...

必须是没有官方支持的GCC选项。



      以下为原文

    Must be a GCC option that's not officially supported.
 

对不起，错过了信息。使用：-STD= GNU99作品



      以下为原文

    Sorry, missed the info.
 
using:
 
-std=gnu99
 
Works

仔细设置时，“附加选项”，由于MPLAB X bug，这些都会被删除。这在我身上发生了很多。当你有10个项目打开时，你必须把它们粘贴回去。



      以下为原文

    Careful when setting, "additional options", due to mplab x bugs these can get deleted.
 
It has happened to me a lot.  You have to paste them back in, annoying when you have 10 projects open.

请注意，这会导致编译器支持的语言是“GNU C 99”，这与ISO标准C 99不同。



      以下为原文

   
 
Be aware that this causes the language the compiler supports to be "GNU C 99", which is different from ISO Standard C 99.

你倾向于死亡——一种或另一种方式。



      以下为原文

    You're prone to die - one or another way.

嗨，我用Matlab/Simulink（R）编码器对DSPIC、PIC18和ARM皮质M4（使用KEIL）进行代码生成。我总是提出附加选项：-STD= GNU99，代码工作出色。用这个集合，实现PID、传递函数、状态流、模糊逻辑、卡尔曼滤波等。S附加选项，您可以使用（例如，UINT8YT T＝0；i＆lt；10；i++）。虽然它在Microchip的文献中没有说明，但是使用GNU99标准总是很好的，因为您可以访问共享库，例如使用Matlab/Simulink编码器，可以得到POW。DSPIC内部的Simulink的ER。例如，在ARM中，可以在生成的代码中使用CMSIS库。GNU99还允许使用MISRA-C 2012准则对关键系统进行编程。我建议使用新的数字格式标准，UIT88T而不是无符号char、因特16t而不是Ont等等。



      以下为原文

    Hi, I use Matlab/Simulink(R) coder for code generation for dsPIC, PIC18 and ARM Cortex M4 (using Keil).
I always put the additional option: -std=gnu99, and the code work excellent. 
With this set, implement PIDs, Transfer functions, State flow, Fuzzy Logic, Kalman filter, etc. etc. is too easy.
With this additional option, you can use: for (uint8_t i = 0; i<10; i++), for example.
 
Although it is not stated in the literature of Microchip, it is always good to work with the gnu99 standard since you have access to shared libraries, for example using Matlab / Simulink coder, one gets to have the power of simulink inside the dsPIC. And for example in ARM, it is possible to use the CMSIS libraries in the generated code. GNU99 also allows programming using the MISRA-C 2012 guidelines for critical systems.
 
I recommend using the new standards for numerical formats, uint8_t instead of unsigned char, int16_t instead of int, etc.

#include /* Includes uint16_t definition */
#include /* Includes true/false definition */

 
Regards!