On Wednesday 13 May 2015 20:43:58 André Pönitz wrote: > > a) do nothing, accept and document the source incompatibility > > b) modify differently so that the new API isn't ambiguous but doesn't > > require people to write 0 either. > > Does it have to be an *overload*?
No, it doesn't. That would be one possible solution (b). -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
