On 12/11/21 5:53 AM, 'melcher....@googlemail.com' via fltk.coredev wrote:

You are right, bad example. A different one: If a Declaration node is inside a Class node, Fluid recognises the keywords class, struct, typedef, and FL_EXPORT at the start of the declaration and copies those declarations verbatim to the header file. Otherwise, Fluid will remove all but one spaces between the declaration and a potential inline comment ( `int x=1;       // test` will become `int x=1; // test`).

If anyone can explain that to, that would be quite helpful.

    I'm not looking at the code and not even familiar with it, but I'm guessing it tries
    to remove trailing spaces from the user's declaration code (thinking trailing white is an error),
    but tacks on a trailing space just to make sure comments don't "touch" the code statement,
    so as to avoid 'int x=1;// test'.

    I actually saw github's "diff" error-highlighted comments touching code recently, it was something like:

        void somefunc(int */*xyz*/, ..)

    ..I thought this an interesting trend, and even saw similar warnings from one of the newer
    compilers which warned about possibly confusing indenting..! Everything's getting very
    picky these days (which is probably a good thing). I personally never liked the idea of comments
    being too close to code, as it can be confused for a math formula or similar.