On segunda-feira, 25 de novembro de 2013 13:08:04, André Somers wrote: > Please note that this goes for *any* method that has an overload. And > that any method that currently does not have an overload, may still get > one in the future. If you don't want to run the risk of source > incompatabilities in the future, I'd always use the explicit signature.
We'll pay more attention to this now that we are taking addresses to functions. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
