@ManoloFLTK I'm not a friend of such C comments as used in the old code and the resulting new code after the patch. Such /* ... comments ... */ that span several lines of otherwise valid code are confusing, and at any time a dev adds a new comment inside that sequence of lines the new */ would terminate the previous comment etc. etc..

In such cases I suggest to use either C++ comments // on all commented-out lines or #if (0) ... #endif or similar to make clear what code part is commented out and which part is valid code.

Thanks for taking this into account if you apply the patch.

I can't say anything to the issue at hand or the patch though.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/957/2068146024@github.com>