It's a joke only if you're laughing. Hey, it's no worse than
stringifying/blobbing a C file [0] (which works well in gcc/clang).
All people have done is game cpp and the standard.
#define STRINGIFY(src) #src
inline const char* Kernels() {
static const char* kernels = STRINGIFY(
#include "kernels/util.cl"
#include "kernels/basic.cl"
);
return kernels;
}
[0]
http://stackoverflow.com/questions/6502173/preprocessor-tomfoolery-stringifying-a-include
On Thu, Nov 6, 2014 at 9:45 AM, FRIGN <d...@frign.de> wrote:
> On Thu, 6 Nov 2014 09:34:17 -0800
> Louis Santillan <lpsan...@gmail.com> wrote:
>
>> There is one case where C++ style comment create a useful feature that I
>> don't believe C style comments are able to replicate. Some might disagree.
>> In a color syntax highlighting editor in a C99 codebase, you can prefix C
>> style comments with C++ style comments and get single character feature
>> enable/disabling.
>>
>> //* Remove first / to disable this block
>> doSomething();
>> //*/
>>
>> In a color syntax highlighting editor, doSomething(); takes on normal
>> highlighting when enabled, and takes on comment colored highlighting when
>> disabled.
>
> Is this a joke?
>
> --
> FRIGN <d...@frign.de>
>
