On Wednesday, 4 October 2017 09:30:46 PDT Thiago Macieira wrote: > It would have, if you hadn't explicitly cast the difference away. A lot of > Glib-using code does that because of GCallback and G_CALLBACK. > > Avoid those like the plague, except for functions that really take no > arguments and return void. Any other use is flawed by design.
In other words, the only place you should use G_CALLBACK is where you don't need to use it. If your code compiles without G_CALLBACK, it is correct. If you needed G_CALLBACK, then you might have hid a problem from the compiler. In other words, anywhere where you need G_CALLBACK is a flawed design. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
