@ManoloFLTK Shallow copy means that pointers are copied verbatim, but the data that they are pointing to is not copied. So if you use a string as a parameter, it must be retained by the caller. I figure out how to improve on that. Anyway, I will document what I mean by "shallow copy".

The second parameter of FL_INLINE_CALLBACK is simply a function body including the leading '{' and trailing '}'. I will rephrase this part of the docs. All the macro handling seems to work just fine.

A common case where macros fail is with templates. For example test<a,b> as an argument for macros is interpreted as two parameters, test<a and b> thanks to the comma. But this does not apply here, so I can remove the cautious documentation line.

—
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/pull/729/c1541609729@github.com>