Actually, "string constant concatenation" is handled by cccc -
when it can recognize it as such. Remember - cccc works on
_"un-preprocessed"_ input, and thus sees __DATE__ and
__TIME__ as identifiers - making this an [apparently] illegal
construct.
A suggested work-around for this would be something like :
Logged In: YES
user_id=1237437
Actually, "string constant concatenation" is handled by cccc -
when it can recognize it as such. Remember - cccc works on
_"un-preprocessed"_ input, and thus sees __DATE__ and
__TIME__ as identifiers - making this an [apparently] illegal
construct.
A suggested work-around for this would be something like :
#define __DATE_TIME__ __DATE__ " " __TIME__
const char* _buildx = __DATE_TIME__;
...thus resolving it within the preprocessor for the compiler,
and "hiding" the "apparent syntax error" from cccc.
Regards,
- Jake