I suppose the issue is that it is something that you need to know what you are doing to use it, as you are directly changing (by adding) code to task.c
In case you havn’t figured out what it does, it makes task.c do a include for the file freertos_task_c_additions.h which can then do things with the “private” definitions defined in task.c.
Thanks for the suggestion! I agree it should be documented. I’m not sure I want to place it on that page of our website as that shows a ‘typical’ FreeRTOSConfig.h example. The use of configINCLUDE_FREERTOS_TASK_C_ADDITIONS_H is less common amongst users. I’ll look into adding a new page or section which explains the config value.
The notion that freertos_task_c_additions.h is user provided was helpful. I now remember why I enabled it. I’m using MCUXpresso IDE. And enabling this configuration allows the IDE “thread aware debugging” and to provide usage data. The freertos_task_c_additions.h is provided by the IDE and SDKs.